|
Exceptional methods can be used to investigate outliers in the performance of selected methods.
Often, certain methods are supposed to complete quickly, but occasionally an invocation will take much
longer than the median time. In the call tree view, you cannot analyze those outliers, since all calls
are cumulated.
When you register a method for exceptional method recording, a few of the slowest invocations will be retained
separately in the call tree. The other invocations will be merged into a single method node as usual.
The number of separately retained invocations can be configured in the
profiling settings, by default it is set to 5.
When discriminating slow method invocations, a certain thread state can be used for the time measurement.
By default, the wall clock time (all thread states) is used, but a different thread status can be configured
in the profiling settings. Note that the thread status selection
in the CPU views is not used in this case, but the separate setting in the
profiling settings is used.
|