[ https://issues.apache.org/jira/browse/IGNITE-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259975#comment-15259975 ]
Semen Boikov commented on IGNITE-3057: -------------------------------------- Valentin, I reviewed your changes, for 'get' inside serializable transactions we need to check that entry version did not change when tx is comitted, so 'fast finish' path can not be used. I fixed this and also added sanity test for 'fast finish' txs. > Optimize transactions that do not acquire any locks > --------------------------------------------------- > > Key: IGNITE-3057 > URL: https://issues.apache.org/jira/browse/IGNITE-3057 > Project: Ignite > Issue Type: Bug > Components: cache > Affects Versions: 1.5.0.final > Reporter: Valentin Kulichenko > Assignee: Valentin Kulichenko > Fix For: 1.6 > > > There are cases when a transaction did not acquire any locks (e.g., > optimistic read-only transaction). In this case we can simply remove > transaction from the local transaction manager, but we are going through all > the steps, like prepare and commit/rollback. > This optimization can give serious benefit in read-most use cases, like > caching. -- This message was sent by Atlassian JIRA (v6.3.4#6332)