Garbage collection perspective

Identify memory leaks and review suggested tuning parameters.

Garbage collection is a system of automatic memory management. Memory that has been dynamically allocated but that is no longer in use is reclaimed without intervention by the application. Garbage collection solves the problem of determining object liveness by freeing memory only when it becomes unreachable.

Garbage collection offers many benefits in terms of application robustness and performance. A runtime environment might auto-tune garbage collection but explicit tuning can improve performance or bring application behavior in line with quality of service requirements. You can also use garbage collection to identify applications that are not running properly. Excessive memory consumption can have a significant performance affect. A memory leak can cause an application to fail.

The Health Center attempts to suggest tuning parameters and identify memory leaks.

Enabling the garbage collection perspective

Enable the garbage collection perspective:
  1. Connect to a runtime environment that is running a suitable monitoring agent.
  2. For Java™ applications only: open the binary trace log from a Java runtime environment that is running the Health Center agent .
For Java applications, more detailed garbage collection information is available from IBM® SDK, Java Technology Edition Version 6 than from IBM SDK, Java Technology Edition Version 5.




© Copyright IBM Corporation 2007, 2016.
© Copyright 1997, 2016, Oracle and/or its affiliates.
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.