Fully featured low overhead profiler for Java EE and Java SE platforms.
Easy to use performance and memory .NET profiler for Windows and Linux.
Performance monitoring and profiling of Jenkins, Bamboo, TeamCity, Gradle, Maven, Ant and JUnit.

Instructions on how to control data from the computer explor

Moderators: Vladimir Kondratyev, Anton Katilin

Instructions on how to control data from the computer explor

Postby thanhvanchi » Tue Dec 20, 2016 9:55 am

Dear all member!

I have a few questions about the probe data retention and control.

1. Can the probe data be retained on the same schedule as the telemetry data (controlled by telemetrylimit=<hours>) ?

For some types of probes, e.g. JDBC, Socket, Thread, I would the probe data to show only the activity that occurred in the visible time range shown in the Thread View. As stacktrace/telemetry data is pruned from the ThreadView, the probe data for those time periods should also be pruned.

The current behavior works fine when I am profiling the startup of the application or the 1st hour, but when I am looking at the behavior in the 24th hour after startup, the probe data either has already reached retention limit (yjp.probe.table.length.limit), or if it still recording in the current hour, in can be hard to analyze because the ThreadView only has the current hour but the probe data has 24 hours.

Because all probe data is retained, I am having to set yjp.probe.table.length.limit to some extreme values from internet e.g. 5,000,000 to try to capture the behavior in the 24th hours. Also, to stretch the probe data capacity, I turn off all probes I'm not interested in. For example, if I am looking into database related issue, I will set it startup options builtinprobes=none,probe=com.yourkit.probes.builtin.Databases.

The main way I look at the probe data is using the Call Tree on the Probes tab. The Call Tree is much harder to look at when it contains everything since startup, but you are only looking at the current hour.

2. Can we turn collection of probe data on and off, similar to what we can do for cpu sampling and object allocation?

3. Can we clear probe data?

Thank's a lot!
Posts: 2
Joined: Tue Dec 20, 2016 9:36 am

Re: Instructions on how to control data from the computer ex

Postby Anton Katilin » Tue Dec 20, 2016 11:22 am


1. No. Unlike the telemetry graphs that limit themselves automatically, probe recording begins and ends explicitly.

2. "Can we turn collection of probe data on and off, similar to what we can do for cpu sampling and object allocation?"


By default, most probes are in the Auto activity mode. This means they start recording when CPU profiling starts, end stop recording when it ends.

You can also activate/deactivate probes explicitly.

3. "Can we clear probe data?"


Probe data, if any, automatically clears when probe activates (e.g. when CPU profiling starts).

As a workaround/solution, you may capture snapshots periodically and clear probe data.

Best regards,
Anton Katilin
Posts: 6027
Joined: Wed Aug 11, 2004 8:37 am

Return to Java Profiler

Who is online

Users browsing this forum: No registered users and 1 guest

YourKit uses cookies and other tracking technologies to improve your browsing experience on our website, to show you personalized content and targeted ads, 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.