What is the use of MetaSpace in Java 8?

Question

I know they have replaced PermGen with MetaSpace in Java 8. But I have few questions:

1. Is MetaSpace by default is GC collected?
2. Even the PermGen is GC collected by adding the args like -XX:+CMSClassUnloadingEnabled, then what makes MetaSpace better than PermGen?
3. MetaSpace is based on native memory, so it keeps the java objects on the disks rather than on VM?
4. Even MetaSpace can run out of memory? If so again I will get OutOfMemoryException.
5. By default the MetaSpace can grow on increase in memory?

Thanks in advance

Answer 1

1. Is MetaSpace by default is GC collected?

   Garbage collection of the dead classes and classloaders is triggered once the class metadata usage reaches the “MaxMetaspaceSize” which by default is "unlimited" so a proper monitoring is required to limit the delay or frequency of such GC.

2. Even the PermGen is GC collected by adding the args like -XX:+CMSClassUnloadingEnabled, then what makes MetaSpace better than PermGen?

   The main goal is removing permgen was so that users do not have to think about correctly sizing it.

3. MetaSpace is based on native memory, so it keeps the java objects on the disks rather than on VM?

   Disk is not native memory but storage device. Native memory, in this context is the area, is the memory for the process left over from the Java heap

4. Even MetaSpace can run out of memory?

   Yes, it is limited by the amount of memory in your machine.

Answer 2

Is MetaSpace by default is GC collected?

Yes, GC will run on metaspace when its getting full, it would also dynamically increase (given its allowed to) the memory allocated for metadata.

Even the PermGen is GC collected by adding the args like -XX:+CMSClassUnloadingEnabled, then what makes MetaSpace better than PermGen?

The improvement is with the dynamic expansion of the metaspace which is something permgen wasn't able to do.

MetaSpace is based on native memory, so it keeps the java objects on the disks rather than on VM?

Based on the description of metaspace, it only uses the native memory (no paging).

Based on the research by Pierre - Hugues Charbonneau (link here) its clear that the introduction of metaspace doesn't necessarily solve the OOM issue, its a bandaid to the problem at best, it attempts to dynamically resize the metaspace memory to accomodate the growing number of classes which get loaded with a possible side effect of growing uncontrollably (so long as the native memory permits it).

We can achieve the famed OOM error by setting the MaxMetaspaceSize argument to JVM and running the sample program provided.

many thanks to Pierre - Hugues Charbonneau.

Answer 3

In response:

1. By default the Metaspace memory is collected if it reaches the MaxMetaspaceSize. This parameter is initially unlimited. The limit is the memory in your machine. But the memory is automatically freeded when a class and class loader is no longer needed. You only need to tune this parameter if you suspect that the ClassLoader has a memory leak.

2. The MetaSpece use native memory and the organization in memory with pointers makes that the GC are faster than older PermGen memory.

3. No, it means that the JVM use the memory like common C program and don't use the virtual memory space for java objects. That seems that the memory is only limited by the machine. Take care that the memory of the machine can be swapped to disk if needed.

4. If you set the parameter MaxMetaspaceSize you can get OutOfMemory and, if you don't set this parameter you can get if the process allocate all the machine memory (including swap space).