[infinispan-dev] Repeatable reads and WSC as default
Radim Vansa
rvansa at redhat.com
Fri Feb 24 08:53:33 EST 2017
Hi all,
I am writing a bit too late in 9.0 cycle, but since I've found couple of
bugs [1][2] and spaces for improvement [3][4] in WSC implementation, I
was wondering about confirming the performance effect of fixes. And I am
wondering if the current defaults for transactional cache, being
READ_COMMITTED and WSC off are the best options.
During 8.0 cycle Tristan raised a discussion [5] including WSC defaults
and I think that the general opinion was "make it default", which
requires RR isolation and simple versioning scheme. But I think that the
whole thing [6] went a bit forgotten and all that was done is [7].
Do we want to do this, at least using current API? (we most likely don't
want to refactor ConfigurationBuilder when CR2 is out)
Radim
[1] https://issues.jboss.org/browse/ISPN-7526
[2] https://issues.jboss.org/browse/ISPN-7527
[3] https://issues.jboss.org/browse/ISPN-7528
[4]
https://github.com/infinispan/infinispan/blob/master/core/src/main/java/org/infinispan/container/entries/ClusteredRepeatableReadEntry.java#L30
could be a contention point
[5]
http://infinispan.markmail.org/message/rasqqkojwdboql7y?q=write+skew+list:org%2Ejboss%2Elists%2Einfinispan-dev+order:date-backward
[6] https://issues.jboss.org/browse/ISPN-3927
[7] https://issues.jboss.org/browse/ISPN-7507
--
Radim Vansa <rvansa at redhat.com>
JBoss Performance Team
More information about the infinispan-dev
mailing list