Garbage-first collector

The Garbage-First Collector (G1) is a garbage collection algorithm introduced in the Oracle HotSpot Java virtual machine (JVM) 6 and supported from 7 Update 4. It was planned to replace Concurrent mark sweep collector (CMS) in JVM 7 and was made default in Java 9.[1]

Garbage collector

Garbage-first (G1) collector is a server-style garbage collector, targeted for multiprocessors with large memories, that meets a soft real-time goal with high probability, while achieving high throughput.[2] G1 preferentially collects regions with the least amount of live data, or "garbage first".[3] G1 is the long term replacement of CMS. Whole-heap operations, such as global marking, are performed concurrently with the application threads, to prevent interruptions proportional to heap or live-data size. Concurrent marking provides both collection completeness and identifies regions ripe for reclamation via compacting evacuation. This evacuation is performed in parallel on multiprocessors, to decrease pause times and increase throughput.

G1 was first introduced as an experimental option in Java SE 6 Update 14,[4] where it can be enabled with the following two command-line parameters: -XX:+UnlockExperimentalVMOptions and -XX:+UseG1GC With JDK 7, G1 was planned to replace CMS in the Hotspot JVM. There are two major differences between CMS and G1. The first is that G1 is a compacting collector.[5] G1 compacts sufficiently to completely avoid the use of fine-grain free lists for allocation, which considerably simplifies parts of the collector and mostly eliminates potential fragmentation issues. As well as compacting, G1 offers more predictable garbage collection pauses than the CMS collector and allows users to set their desired pause targets.

Proposals for Java 9 included making G1 the standard garbage collector, with Google counter proposing the well-known CMS as the standard, claiming the modified CMS it uses performs better than G1.[6]

In Java 9 the G1 was made the default garbage collector.[7][1]

Guaranteed real-time behavior even with garbage collection requires a real-time garbage collector such as those that come with Sun's Java RTS[8] or IBM’s WebSphere RT.[9]

gollark: Luca_S: Does potatOS print anything before wiping itself?
gollark: Can you see the fnords?
gollark: The fnords.
gollark: @Keanu73 *I know.*
gollark: Sorry, I understand no numbers except those relating to production of materials.

See also

References
  1. "JEP 248: Make G1 the Default Garbage Collector". openjdk.java.net. Retrieved 2019-12-09.
  2. Detlefs, David; Flood, Christine; Heller, Steve; Printezis, Tony (2004). "Garbage-First Garbage collection". Ismm'04: 37. CiteSeerX 10.1.1.63.6386. doi:10.1145/1029873.1029879. ISBN 1581139454.
  3. "Part 1: Introduction to the G1 Garbage Collector". www.redhat.com.
  4. "G1: Java's Garbage First Garbage Collector". Dr Dobbs.
  5. "The Garbage First Collector". www.fasterj.com.
  6. "Java 9's new garbage collector: What's changing? What's staying? - JAXenter". jaxenter.com. 26 June 2015.
  7. "Why G1 is default garbage collector for Java 9?".
  8. http://www.oracle.com/technetwork/articles/javase/index-138577.html An Introduction to Real-Time Java Technology: Part 2, Garbage Collection and the Sun Java Real-Time System (Java RTS)
  9. http://www.ibm.com/developerworks/java/library/j-rtj4/index.html?S_TACT=105AGX02&S_CMP=EDU Real time Garbage Collection
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.