Getting rid of all locking would be great. Assuming my read of the code is correct, and the locking is just to make sure the value does not change, I was thinking of a sub optimization for my specific problem ( there being very few unique keys in the cache ) . Loop through the cache in reverse order ( most recent entry first ) and look at a key but only lock it if it is the first time you see the key. Any time you see a duplicate key you could ignore it without getting a lock, since you already have a more recent value. For the case where there are lots of updates to the same key this would eliminate a lot of the locking. In the interim we have solved this issue by buffering the writes to this key in our code ( effectively our own collation ).
On Mon, Nov 13, 2017 at 3:33 AM, Alexey Popov <tank2.a...@gmail.com> wrote: > Hi Larry, > > BTW, there is an open improvement > https://issues.apache.org/jira/browse/IGNITE-5003 > for the issue you faced. > > Thanks, > Alexey > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
