Hi Val, Lately I was using optimistic serializable which has better performance in my test cases.
I see two problems with EntryProcessor: 1. When the "where" condition is generic I don't have the keys therefore an initial step is required to move all the keys in the client. 2. In my tests putAll performs better than EntryProcessor. Apparently EntryProcessor#process is called in the client too. I don't know what triggers loading the value + processing in the client. >From what I saw there is no way for changes done inside IgniteCallable to be enlisted in the transaction started in the client. Can you confirm that? Thanks, Ionut -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Update-performance-tp6214p6255.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
