RFR: Enable biased locking for Shenandoah by default

Andrew Haley aph at redhat.com
Mon Nov 20 14:11:52 UTC 2017


On 20/11/17 12:01, Aleksey Shipilev wrote:
> Few thoughts here:
> 
>  *) Biased locking is inherently orthogonal to GC code, and is not visible even in gross GC pauses.
> Therefore, we have no observable improvements, as far as GC logging is concerned. (This is different
> for loop strip mining, that does improve gross pause times);
> 
>  *) With the throughput hit we observe, it makes less sense to focus on orthogonal VM pauses.

But biased-locking revocation does affect pause times.  Do we know
how the worst-case pause times with Shenandoah's CG-related
pauses compare with revocation pauses?

-- 
Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671


More information about the shenandoah-dev mailing list