[concurrency-interest] regarding StampedLock

Dr Heinz M. Kabutz heinz at javaspecialists.eu
Tue Oct 16 19:00:08 EDT 2012

The readers are probably tag-teaming each other, just like they did in Java 5.

On 17/10/2012, Doug Lea <dl at cs.oswego.edu> wrote:
> On 10/15/12 11:34, Dr Heinz M. Kabutz wrote:
>> my performance test is based on some starvation research I did in 2008
>> regarding
>> ReadWriteLock: http://www.javaspecialists.eu/archive/Issue165.html
> I'm still exploring some different policy options, but here's a quick
> note on your test: If you report locks per thread, rather than total locks,
> then starvation tendencies across varying numbers of readers vs writers
> (keeping total the same) are easier to describe: For a writer, you expect
> approximately the same lock rate whether the other locking threads are
> readers vs writers. The overall rates may differ across different hold
> times etc but for each choice, this property should hold for
> starvation-avoiding RW Locks.  (A similar but less simple property
> should hold for readers.)
> -Doug

Dr Heinz M. Kabutz (PhD CompSci)
Author of "The Java(tm) Specialists' Newsletter"
Sun Java Champion
IEEE Certified Software Development Professional
Tel: +30 69 75 595 262
Skype: kabutz

More information about the Concurrency-interest mailing list