Optimistic should show better performance than pessimistic transactions. The main point about OPTIMISTIC READ_COMMITTED is that during a commit it’s not checked if an entry value has been modified since the first read or write access and an optimistic exception is never raised. However OPTIMISTIC SERIALIZABLE will detect such a situation and throw the optimistic exception allowing you to perform a transaction one more time.
You can read more on optimistic modes here: https://apacheignite.readme.io/v1.6/docs/transactions#optimistic-transactions <https://apacheignite.readme.io/v1.6/docs/transactions#optimistic-transactions> https://apacheignite.readme.io/v1.6/docs/transactions#deadlock-free-transactions <https://apacheignite.readme.io/v1.6/docs/transactions#deadlock-free-transactions> — Denis > On Jun 16, 2016, at 7:29 PM, amitpa <[email protected]> wrote: > > Does OPTIMISTIC Serializable give better performance? > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-performance-improvements-tp5623p5684.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com.
