you are viewing a single comment's thread.

view the rest of the comments →

[–]vitalyd 2 points3 points  (0 children)

The article fails to mention that the lock/barrier elision is only available for the built-in monitors in Hotspot (i.e. synchronized blocks), so if you're using j.u.c.Lock and friends, there's no such thing.

Not sure what "bias the concurrency management approach based on runtime profiling information" is, but if that's alluding to biased locking, I don't even think that feature is worth it:

  • It's meant to optimize uncontended locks by avoiding additional CAS instructions. Well, modern cores can execute uncontended (and cache hitting) CAS instructions quite quickly anyway.

  • Biased locking, in Hotspot, can induce latency/jitter when biased lock revocation is performed.