Hi Eric, Can you please suggest any new performance tuning options for G1GC. We recently started migrating from CMS to G1GC which resulted in performance issues due to humongous objects. We went with 32M region size, still performance issue is not fixed. Please let me know if there are any special options to handle humongous objects.
Humongous object are the size of more than half of the region size. Let's say if my object some is 3MB and the region size is only 2MB. Where does this object gets allocated?? Will the size of the region gets resized automatically??
Really good intro before getting into detailed explanation.
Hi Eric, Can you please suggest any new performance tuning options for G1GC. We recently started migrating from CMS to G1GC which resulted in performance issues due to humongous objects. We went with 32M region size, still performance issue is not fixed. Please let me know if there are any special options to handle humongous objects.
Hi, what exactly compactly copied means?
How can I get the slides?
Humongous object are the size of more than half of the region size. Let's say if my object some is 3MB and the region size is only 2MB. Where does this object gets allocated?? Will the size of the region gets resized automatically??
Regions cannot be resized. As far as I understand, this 3MB object will be allocated in two consecutive humongous regions.
Yes, this is mentioned in Q&A session.
It starts at 23:30
How region created in JVM ?
Regions are an analogy to how G1GC sees the HEAP , which is simply a pseudo-continuous memory space.