RFR: bug: Timely Reducing Unused Committed Memory

Per Liden per.liden at oracle.com
Fri Sep 7 08:46:06 UTC 2018

Hi Thomas,

On 09/07/2018 10:10 AM, Thomas Schatzl wrote:
>    overnight I thought a bit of the implementation, and given the
> problem with heap usage of the new thread, and the requirement of being
> able to turn on/off that feature by a managed variable, the best change
> would probably reusing the service thread as you did in the initial
> change.

I'm not convinced that this should be handled outside of G1. If there's 
a need to have the flag manageable at runtime (is that really the 
case?), you could just always start the G1DetectIdleThread and have it 
check the flag. I wouldn't worry too much about the memory overhead for 
the stack.


More information about the hotspot-gc-dev mailing list