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

methods CPU Times

Moderators: Vladimir Kondratyev, Anton Katilin

methods CPU Times

Postby Gustavo Woltmann » Wed Feb 24, 2016 11:48 pm


Could someone explain me why the methods CPU Times are always different when sucessive profilings are made for the same application on the same conditions?

I'm running on Windows Xp, and I tried both sampling and tracing profiling methods.

Thank you.
Gustavo Woltmann
Posts: 2
Joined: Wed Feb 24, 2016 6:36 pm

Re: methods CPU Times

Postby Anton Katilin » Thu Feb 25, 2016 4:41 pm

Do you use sampling or tracing?
Sampling as approximate by its nature.
With tracing, wall time is recorded by default, so any side effects such as other applications running in parallel which which your application shared CPU resources may cause fluctuations:
Anton Katilin
Posts: 5816
Joined: Wed Aug 11, 2004 8:37 am

Return to .NET Profiler

Who is online

Users browsing this forum: No registered users and 1 guest