jwha at google.com
Fri Mar 11 00:06:41 UTC 2016
We've been disabled CMSClassUnloading for a long time and had no issues.
We recently turned it back on by default with
CMSClassUnloadingMaxInterval=5, which amortizes the increased remark cost.
On Thu, Mar 10, 2016 at 1:32 PM, Tony Printezis <tprintezis at twitter.com>
> Hi all,
> CMSClassUnloadingEnabled is enabled by default in JDK 8. Most of our
> services do not require class unloading (they load a bunch of classes
> up-front and that’s it) so we’re thinking of turning it off by default in
> our JDK as it increases our remark times by a non-trivial amount (40-90ms
> depending on the service). Any known issues with running with
> -XX:-CMSClassUnloadingEnabled? (This is a veiled way to ask: is anyone
> testing with that flag off?)
> Tony Printezis | JVM/GC Engineer / VM Team | Twitter
> tprintezis at twitter.com
Jungwoo Ha | Java Platform Team | jwha at google.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the hotspot-gc-dev