Optimizing memory usage across multiple garbage collected computer environments
US-9836394-B2 · Dec 5, 2017 · US
US10372604B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10372604-B2 |
| Application number | US-201816045869-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 26, 2018 |
| Priority date | Jul 18, 2013 |
| Publication date | Aug 6, 2019 |
| Grant date | Aug 6, 2019 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method, information processing system, and computer readable storage medium, periodically monitor, with a processing system, information related to an application's memory usage including a maximum heap memory size, an in use heap memory size, and a garbage collection activity level. Based on determining that the garbage collection activity level is below a first threshold, estimating an amount of memory that can be released from the application by reducing the maximum heap memory size. Based on determining that the estimated amount of memory that can be released from the application is above a second threshold, attempting to release memory from the application.
Opening claim text (preview).
What is claimed is: 1. In a processing system including an application, a run-time system, and a heap memory used by the application, wherein unused memory in the heap memory is reclaimed by a garbage collector, a method for managing memory used by the application comprising: periodically monitoring, with the processing system, information related to the application's memory usage including a maximum heap memory size, an in use heap memory size, and a garbage collection activity level; based on determining that the garbage collection activity level is below a first threshold, estimating an amount of memory that can be released from the application by reducing the maximum heap memory size; and based on determining that the estimated amount of memory that can be released from the application is above a second threshold, releasing memory from the application. 2. The method of claim 1 in which the estimating an amount of memory that can be released from the application by reducing the maximum heap memory size comprises: determining a difference between a committed heap memory size and the in use heap memory size. 3. The method of claim 1 in which the estimating an amount of memory that can be released from the application by reducing the maximum heap memory size comprises: performing a compacting garbage collection; and determining a difference between a committed heap memory size and the in use heap memory size. 4. The method of claim 1 in which releasing memory from the application further comprises: performing a compacting garbage collection to instantiate a reduced value of maximum heap memory size. 5. The method of claim 1 further comprising: increasing the maximum heap memory size to allow the application to allocate more heap memory. 6. The method of claim 1 in which the application comprises a Java virtual machine. 7. The method of claim 1 in which the garbage collection activity level is determined based on at least one of: a time since a garbage collection was performed on the heap memory; a frequency of garbage collection performed on the heap memory; and a time spent in garbage collection performed on the heap memory. 8. The method of claim 1 in which the garbage collection activity level is determined based on at least one of: a time since a compacting garbage collection was performed on the heap memory; a frequency of compacting garbage collection performed on the heap memory; and a time spent in at least one compacting garbage collection performed on the heap memory. 9. The method of claim 1 in which the monitored garbage collection activity level is determined by normalizing a metric representing garbage collection overhead by an amount of processing time spent by the application not including garbage collection. 10. The method of claim 1 , further comprising: providing a plurality of options to a user for specifying a level at which the processing system attempts to reduce memory used by the application. 11. An information processing system comprising: a memory comprising a heap memory for use by at least one application; a processor communicatively coupled to the memory; a garbage collector communicatively coupled to the processor and the memory, wherein unused memory in the heap memory is reclaimed by the garbage collector; and wherein the processor, responsive to executing computer instructions, performs operations comprising: periodically monitoring, with the processing system, information related to the application's memory usage including a maximum heap memory size, an in use heap memory size, and a garbage collection activity level; based on determining that the garbage collection activity level is below a first threshold, estimating an amount of memory that can be released from the application by reducing the maximum heap memory size; and based on determining that the estimated amount of memory that can be released from the application is above a second threshold, releasing memory from the application. 12. The information processing system of claim 11 , in which the estimating an amount of memory that can be released from the application by reducing the maximum heap memory size comprises: determining a difference between a committed heap memory size and the in use heap memory size. 13. The information processing system of claim 11 , in which the estimating an amount of memory that can be released from the application by reducing the maximum heap memory size comprises: performing a compacting garbage collection; and determining a difference between a committed heap memory size and the in use heap memory size. 14. The information processing system of claim 11 , in which the releasing memory from the application further comprises: performing a compacting garbage collection to instantiate a reduced value of maximum heap memory size. 15. The information processing system of claim 11 , wherein the processor, responsive to executing the computer instructions, performs operations comprising: increasing the maximum heap memory size to allow the application to allocate more heap memory. 16. The information processing system of claim 11 , in which the application comprises a Java virtual machine. 17. The information processing system of claim 11 , further comprising a user input interface for receiving user input communications from a user of the information processing system, and a user output interface for providing output communications to the user, and wherein the processor, responsive to executing the computer instructions, performs operations comprising: providing a plurality of options to the user, via the user output interface, for the user to select, via the user input interface, one of the plurality of options to specify a level at which the information processing system attempts to reduce memory used by the application, each option of the plurality of options being associated with a respective one pre-configured parameter setting of a plurality of different pre-configured parameter settings in the information processing system. 18. A computer readable storage medium, comprising computer instructions which, responsive to being executed by a processor cause the processor to perform operations, the processor being in an information processing system comprised of a memory communicatively coupled to the processor, the memory comprising a heap memory, and a garbage collector communicatively coupled to the processor and the memory, wherein unused memory in the heap memory is reclaimed by the garbage collector, and wherein the processor, responsive to executing the computer instructions, performs operations comprising: periodically monitoring, with the processing system, information related to the application's memory usage including a maximum heap memory size, an in use heap memory size, and a garbage collection activity level; based on determining that the garbage collection activity level is below a first threshold, estimating an amount of memory that can be released from the application by reducing the maximum heap memory size; and based on determining that the estimated amount of memory that can be released from the application is above a second threshold, releasing memory from the application. 19. The computer readable storage medium of claim 18 , in which the estimating an amount of memory that can be released from the application by reducing the maximum heap memory size comprises: performing a compacting garbage collection; and determining a difference betwee
Garbage collection, i.e. reclamation of unreferenced memory · CPC title
Erasing, e.g. deleting, data cleaning, moving of data to a wastebasket · CPC title
Improving or facilitating administration, e.g. storage management · CPC title
by allocating resources to storage systems · CPC title
Space efficiency improvement · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.