<\/p>\n
G1 is considered “server-centric” with the following attributes.<\/p>\n
- \n
- G1 uses parallelism which are mostly used in hardware today.The main advantage of G1 is designed in such a way to make use of all available CPU’s and utilize the processing power of all CPU’s and increase the performance and speed in Garbage Collection.<\/li>\n
- Concurrency feature of G1 allows to run Java threads to minimize the heap operations at stop pauses.<\/li>\n
- Next feature which plays a key role in increasing the Garbage Collection is treating the young objects(newly created) and the old objects(which lived for some time) differently.G1 mainly focuses on young objects as they can be reclaimable when traversing the old objects.<\/li>\n
- Heap compaction is done to eliminate fragmentation problems.<\/li>\n
- G1 can be more predictable when compared to CMS.<\/li>\n<\/ul>\n
Features of G1\u00a0Garbage Collector<\/strong><\/p>\n
- \n
- A single contiguous heap which is split into same-sized regions. No separation between younger and older regions.<\/li>\n
- G1 uses evacuation pauses.Evacuation pauses are done in parallel by using all the available processors.<\/li>\n
- G1 uses a\u00a0pause\u00a0prediction model to meet user-defined\u00a0pause\u00a0time targets<\/li>\n
- Like CMS,G1 also periodically performs a concurrent marking phase.<\/li>\n
- Unlike CMS, G1 does not perform a concurrent sweeping phase.<\/li>\n<\/ul>\nHere are some elaborated details<\/div>\n\n
- \n
- Parallelism and Concurrency<\/strong>. G1 takes advantage of the parallelism that exists in hardware today. It uses all available CPUs (cores, hardware threads, etc.) to speed up its \u201cstop-the-world\u201d pauses when an application’s Java threads are stopped to enable GC. It also works concurrently with running Java threads to minimize whole-heap operations during stop-the-world pauses.<\/li>\n
- Generational<\/strong>. Like the other HotSpot GC’s, G1 is generational, meaning it treats newly-allocated (aka\u00a0young<\/em>) objects and objects that have lived for some time (aka\u00a0old<\/em>) differently. It concentrates garbage collection activity on young objects, as they are the ones most likely to be reclaimable, while visiting old objects infrequently. For most Java applications, generational garbage collection has major efficiency advantages over alternative schemes.<\/li>\n
- Compaction<\/strong>. Unlike CMS, G1 performs heap compaction over time. Compaction eliminates potential fragmentation problems to ensure smooth and consistent long-running operation.<\/li>\n
- Predictability<\/strong>. G1 is expected to be more predictable than CMS. This is largely due to the elimination of fragmentation issues that can negatively affect stop-the-world pause times in CMS. Additionally, G1 has a pause prediction model that, in many situations, allows it to often meet (or rarely exceed) a pause time target.<\/li>\n<\/ul>\n<\/div>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
Hi all, Hope everything is going good at your desks; Last night, I was reading new features in Java 1.7 and found some updates in garbage collection mechanism; There are many updates in 1.7 ranges from core vm, i18n, Nimbus for Swings and other enhancements. We have already discussed the…<\/p>\n","protected":false},"author":1,"featured_media":5271,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1154],"tags":[399,580,582,583,584,1089,1090],"class_list":["post-2747","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-java","tag-garbage-collector","tag-jav","tag-java-1-7","tag-java-1-7-g1-garbage-collector","tag-java-7","tag-whats-new-in-java-1-7","tag-whats-new-in-java-7"],"_links":{"self":[{"href":"https:\/\/aasimnaseem.com\/blog\/wp-json\/wp\/v2\/posts\/2747","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aasimnaseem.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/aasimnaseem.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/aasimnaseem.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/aasimnaseem.com\/blog\/wp-json\/wp\/v2\/comments?post=2747"}],"version-history":[{"count":3,"href":"https:\/\/aasimnaseem.com\/blog\/wp-json\/wp\/v2\/posts\/2747\/revisions"}],"predecessor-version":[{"id":5273,"href":"https:\/\/aasimnaseem.com\/blog\/wp-json\/wp\/v2\/posts\/2747\/revisions\/5273"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/aasimnaseem.com\/blog\/wp-json\/wp\/v2\/media\/5271"}],"wp:attachment":[{"href":"https:\/\/aasimnaseem.com\/blog\/wp-json\/wp\/v2\/media?parent=2747"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aasimnaseem.com\/blog\/wp-json\/wp\/v2\/categories?post=2747"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aasimnaseem.com\/blog\/wp-json\/wp\/v2\/tags?post=2747"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- Generational<\/strong>. Like the other HotSpot GC’s, G1 is generational, meaning it treats newly-allocated (aka\u00a0young<\/em>) objects and objects that have lived for some time (aka\u00a0old<\/em>) differently. It concentrates garbage collection activity on young objects, as they are the ones most likely to be reclaimable, while visiting old objects infrequently. For most Java applications, generational garbage collection has major efficiency advantages over alternative schemes.<\/li>\n
- Parallelism and Concurrency<\/strong>. G1 takes advantage of the parallelism that exists in hardware today. It uses all available CPUs (cores, hardware threads, etc.) to speed up its \u201cstop-the-world\u201d pauses when an application’s Java threads are stopped to enable GC. It also works concurrently with running Java threads to minimize whole-heap operations during stop-the-world pauses.<\/li>\n