ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yakov Zhdanov <yzhda...@apache.org>
Subject Re: ReadWriteUpdateLock
Date Tue, 19 Jul 2016 10:56:32 GMT
Hi Vlad!

Thanks for bringing this up.

I looked through concurrency-interest discussion, and I don't think we
should do this in Ignite. At least now. I am not sure if this will give any
advantage since only one thread can acquire UPDATE lock at the same time.
Btw, was there any benchmark published comparing UpdateLock  vs RWLock

I think that in many cases read then update scenarios can be handled with
some kind of volatile or atomic read and then acquiring the ordinary lock
or by CAS operation. For the rest of cases we already have RWLock.

And one more point - nobody asked for it. So, I ask - Does anyone need it
in Ignite?



2016-07-18 22:55 GMT+03:00 Vladisav Jelisavcic <vladisavj@gmail.com>:

> Hi everyone,
> cross-posting from JIRA:
> I recently came across this post:
> http://codereview.stackexchange.com/a/31231
> Do you think ReadWriteUpdateLock is something we can put to good use here
> in Ignite?
> This kind of lock should be more efficient for read-before-write patterns.
> Best regards,
> Vladisav

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message