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.

Call counting

Call counting is one of the lightweight CPU profiling modes.

Unlike other modes only method invocations are counted, neither call stacks nor times are gathered. Use this mode to initially detect possible problems: thanks to its low overhead you may do this even in production.

It's a simple tool for identifying potential performance problems caused by suboptimal algorithms. The approach is based on assumption that methods with a big number of invocations may indicate a performance problem.

Further investigation may involve using CPU tracing or sampling to get comprehensive profiling results including times and stack traces (call tree).

Use profiler toolbar to start call counting as shown on the picture below. There are also alternate methods to start CPU profiling.

Overhead

Call counting is specially designed to have minimal possible, almost zero overhead:

  • It provides a plain method list with method invocation counts. Unlike other CPU profiling modes it does not provide stack traces nor method times.
  • Method invocations from different threads are summed and cannot be distinguished.
  • The probes in Auto activity mode are not activated in call counting, thus high-level statistics is not collected.

See also: Profiling overhead: how to reduce or avoid.

Call counting settings

Call counting will be disabled if the startup option disabletracing or disableall is specified.

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.