RFR (XS) 8230646: Epsilon does not extend TLABs to max size

Aleksey Shipilev shade at redhat.com
Thu Sep 5 11:33:52 UTC 2019


I was playing with performance benchmarks and noticed that Epsilon does not extend issued TLABs to
max tlab size, because of the simple overlook. TLAB allocation path asks GC about the max tlab size
currently available with unsafe_max_tlab_alloc(). But, in Epsilon code, there is discrepancy: the
caller interprets the returned value in bytes, while Epsilon code has the size in words. Every other
GC adjusts accordingly, Epsilon should too.


Testing: gc/epsilon, jdk-submit


More information about the hotspot-gc-dev mailing list