IBM User Guide for Java V7 on Windows > IBM SDK for Java > The collector and the allocator

How to coexist with the Garbage Collector

Use this background information to help you diagnose problems in the coexistence of your applications with the Garbage Collector (GC).

Do not try to control the GC or to predict what will happen in a given garbage collection cycle. This unpredictability is handled, and the GC is designed to run well and efficiently inside these conditions.

Set up the initial conditions that you want and let the GC run. It will behave as described in Garbage collection summary, which is in the JVM specification.

• Root set
  The root set is an internally derived set of references to the contents of the stacks and registers of the JVM threads and other internal data structures at the time that the Garbage Collector was called.
• Thread local heap
  The Garbage Collector (GC) maintains areas of the heap for fast object allocation.
• Bug reports
  Attempts to predict the behavior of the Garbage Collector (GC) are frequent underlying causes of bug reports.
• Finalizers
  The Java™ service team recommends that applications avoid the use of finalizers if possible. The JVM specification states that finalizers are for emergency clear-up of, for example, hardware resources. The service team recommends that you use finalizers for this purpose only. Do not use them to clean up Java software resources or for closedown processing of transactions.
• Manually starting the Garbage Collector
  Manually starting the Garbage Collector (GC) can degrade JVM performance.

Parent: The collector and the allocator

Error 404 - Not Found

The document you are looking for may have been removed or re-named. Please contact the web site owner for further assistance.