Java Concurrent Mark and Sweep Collector: Difference between revisions
Jump to navigation
Jump to search
(Created page with "=Internal= * Java Garbage Collection =Overview= The Concurrent Mark Sweep (CMS) collector, is also referred to as the concur...") |
No edit summary |
||
| Line 1: | Line 1: | ||
=Internal= | =Internal= | ||
* [[ | * [[Java_Memory#Garbage_Collectors|Java Memory]] | ||
=Overview= | =Overview= | ||
The Concurrent Mark Sweep (CMS) collector, is also referred to as the concurrent low pause collector. It only collects the old generation. The main reason to use it is to minimaze the "stop-the-world" pauses by doing most of the garbage collection work concurrently with the application threads. Normally the concurrent low pause collector does not move, copy or compact the live objects. | The Concurrent Mark Sweep (CMS) collector, is also referred to as the concurrent low pause collector. It only collects the old generation. The main reason to use it is to minimaze the "stop-the-world" pauses by doing most of the garbage collection work concurrently with the application threads. Normally the concurrent low pause collector does not move, copy or compact the live objects. | ||
Latest revision as of 02:12, 22 April 2017
Internal
Overview
The Concurrent Mark Sweep (CMS) collector, is also referred to as the concurrent low pause collector. It only collects the old generation. The main reason to use it is to minimaze the "stop-the-world" pauses by doing most of the garbage collection work concurrently with the application threads. Normally the concurrent low pause collector does not move, copy or compact the live objects.