[
https://issues.jboss.org/browse/ISPN-1748?page=com.atlassian.jira.plugin....
]
Mircea Markus commented on ISPN-1748:
-------------------------------------
after implementing this I've run some benchmarks and figures don't look at all
encouraging.
Allow consistency for concurrent updates when syncCommitPhase=false
-------------------------------------------------------------------
Key: ISPN-1748
URL:
https://issues.jboss.org/browse/ISPN-1748
Project: Infinispan
Issue Type: Enhancement
Components: Transactions
Affects Versions: 5.1.0.CR4
Reporter: Mircea Markus
Assignee: Mircea Markus
Labels: performace
Fix For: 5.1.0.FINAL
when syncCommitPhase=false then there is a window of inconsistency in the case multipel
tx access the same key at the same time.
This can be avoided by sending the lock release command after the commit command, in the
same thread which is async triggered by the TM.commit.
This should be a very important performance buster for default configurations.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira