RFR(S): 8213086: Compiler thread creation should be bounded by available space in memory and Code Cache

Doerr, Martin martin.doerr at sap.com
Mon Oct 29 16:26:54 UTC 2018

Hi Tobias,

thank you for filing https://bugs.openjdk.java.net/browse/JDK-8213086

I have changed the description because the available memory doesn't get respected due to missing braces. So I'd like to fix this in addition.
My test machines have too much memory to hit this case. Maybe I should try to use a docker container for testing.

My initial proposal allows up to one compiler thread per 128kB of free code cache. I remember that Oracle wants to have many threads (for some SPARC scenarios) so I have chosen a small size.
I'm currently ignoring that C1 also creates some small non-profiled nmethods.

Please review:

Best regards,

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/attachments/20181029/b7633d0d/attachment.html>

More information about the hotspot-compiler-dev mailing list