Java Garbage Collection Concepts: Difference between revisions
No edit summary |
|||
| Line 18: | Line 18: | ||
It can be limited by <tt>MaxMetaspaceSize</tt>. If the flag is not specified, the metaspace will resize. | It can be limited by <tt>MaxMetaspaceSize</tt>. If the flag is not specified, the metaspace will resize. | ||
Increase the initial size of the metaspace: | |||
<tt> | |||
-XX:MetaspaceSize=100M | |||
</tt> | |||
Increase the boot class loader metaspace: | |||
<tt> | |||
-XX:InitialBootClassLoaderMetaspaceSize=32M | |||
</tt> | |||
Growth parameters: | |||
<tt> | |||
-XX:MinMetaspaceFreeRatio=50 | |||
-XX:MaxMetaspaceFreeRatio=80 | |||
-XX:MinMetaspaceExpansion=4M | |||
-XX:MaxMetaspaceExpansion=16M | |||
</tt> | |||
==Garbage Collection== | |||
Garbage collection of the dead classes and classloaders is triggered once the class metadata usage reaches the “MaxMetaspaceSize”. | |||
==Monitoring== | ==Monitoring== | ||
<font color=red>It is considered part of the heap?</font> | <font color=red>It is considered part of the heap?</font> | ||
Revision as of 07:43, 16 February 2017
Internal
Permanent Generation
Metaspace
Overview
The metaspace has been introduced by Java 8 to replace permanent generation. Most allocations for the class metadata are now allocated out of native memory.
Capacity
By default the metaspace can extend to the limit of the physical memory.
It can be limited by MaxMetaspaceSize. If the flag is not specified, the metaspace will resize.
Increase the initial size of the metaspace:
-XX:MetaspaceSize=100M
Increase the boot class loader metaspace:
-XX:InitialBootClassLoaderMetaspaceSize=32M
Growth parameters:
-XX:MinMetaspaceFreeRatio=50 -XX:MaxMetaspaceFreeRatio=80 -XX:MinMetaspaceExpansion=4M -XX:MaxMetaspaceExpansion=16M
Garbage Collection
Garbage collection of the dead classes and classloaders is triggered once the class metadata usage reaches the “MaxMetaspaceSize”.
Monitoring
It is considered part of the heap?