Fully featured low overhead profiler for Java EE and Java SE platforms.
Easy-to-use performance and memory .NET profiler for Windows, Linux and macOS.
Secure and easy profiling in cloud, containers and clustered environments.
Performance monitoring and profiling of Jenkins, Bamboo, TeamCity, Gradle, Maven, Ant and JUnit.

Excessive garbage allocation

How to find excessive garbage allocation?

Purpose: Reduce time that garbage collector spends on collecting temporary objects.

  1. Run application with the profiler.
  2. Connect to the application.
  3. Object allocation telemetry will help you estimate garbage collector load.

If garbage collection takes a significant amount of time, it is advised to profile memory allocation to pinpoint and optimize the problematic code.

Let us assume there is a task in your application that you want to profile.

  1. Start object allocation profiling with default settings right before the task is started.
  2. Wait until the task finishes or performs long enough.
  3. Capture memory snapshot and stop object allocation profiling.
  4. Open snapshot and use Allocations view.

Optionally, the profiled application can be launched with object allocation profiling with the help of corresponding agent startup options. Snapshot with recorded allocation information can be captured automatically on profiled application exit and/or on high memory usage. Read more in the Agent startup options section.

YourKit uses cookies and other tracking technologies to improve your browsing experience on our website, to show you personalized content, to analyze our website traffic, and to understand where our visitors are coming from.

By browsing our website, you consent to our use of cookies and other tracking technologies in accordance with the Privacy Policy.