Dispatcher of Java virtual machine-based concurrent garbage collector

Abstract

The invention belongs to the technical field of Java virtual machine garbage collection and in particular relates to a dispatcher of a Java virtual machine-based concurrent garbage collector. The dispatcher triggers a garbage collection process at a proper time point mainly by dynamically analyzing the running status of the current application program. The dispatcher judges whether to trigger garbage collection by using a simple time reckoning method when the application program applies for a memory every time. The dispatcher also deals with the condition that the memory resources of a system are exhausted at the same time. As a part of a concurrent garbage collecting and unifying frame, the invention provides the garbage collection dispatcher with low cost and high performance, optimizes a trigger point of garbage collection, improves the operation efficiency of the garbage collector and also greatly reduces the probability that the memory resources of the system are exhausted.

Description

technical field [0001] The invention belongs to the technical field of Java virtual machine garbage collection, and in particular relates to a scheduler of a Java virtual machine-based concurrent garbage collector. Background technique [0002] With the rise of high-level programming languages ​​such as Java, how to make reasonable use of memory has become one of the most critical considerations when providing environmental support for various high-level languages. As the main means of memory utilization, garbage collection technology plays an increasingly important role in system security and resource management. [0003] Concurrent garbage collection (Concurrent GC) has emerged as modern applications use larger amounts of memory, the number of objects increases, and the pauses caused by cutting "stop the world" garbage collection seriously affect the response time of the application. This technology enables the garbage collector to perform garbage collection while the ap...

AI Technical Summary

Problems solved by technology

[0004] However, when the concurrent garbage collector is triggered becomes a problem: because if the garbage collection occurs when the system memory is still very free, the system is not fully utilized memory resources and cause the frequency of garbage collection to be too high, which will affect application performance; if it occurs when the system memory is already tight, the system heap memory is likely to be exhausted before concurrent garbage collection is completed, thus forcing garbage collection The collector performs "exhaustion processing" and needs to be forced to stop the application, which undoubtedly increases the pause time of the application

Images