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.

Performance charts timeframe

Moderators: Vladimir Kondratyev, Anton Katilin

Performance charts timeframe

Postby rkamboj » Thu Apr 12, 2018 4:07 am

I created a CPU_SAMPLING snapshot for 10 mins and verified from log file that START_CPU_SAMPLING_PROFILING and STOP_CPU_SAMPLING_PROFILING are 10 mins apart. However, the performance charts have graphs for 25 min duration ...why is that the case
Posts: 2
Joined: Wed Apr 04, 2018 8:39 pm

Re: Performance charts timeframe

Postby Anton Katilin » Thu Apr 12, 2018 7:06 am

Performance charts and other telemetry graphs are stored independently from CPU profiling results.

The telemetry information is remembered in a circular buffer in the profiler agent memory. This allows you to connect to a profiled application on demand and discover how the application behaved in the past.

By default, the telemetry buffer is limited to store approximately 1 hour of recent telemetry data.
Anton Katilin
Posts: 6027
Joined: Wed Aug 11, 2004 8:37 am

Return to Java Profiler

Who is online

Users browsing this forum: Google [Bot] 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.