Caller reports

You can use the Performance Measurement tool to generate caller reports, which identify the source of the calls to run an operation. With these reports, you can analyze operations and identify the sources for numerous calls for the operation to run.
Each caller node within a caller report contains the following information:
<caller
call-count="20"
average-call-count="1.00"
operation-name="child"
average-duration-ms="25"
average-size="1577"
unique-caller-count="4.0">
Where,
call-count
The number of times that this operation executes and results in a call to the identified operation.
average-call-count
The number of times that the operation is called during each execution of the parent caller operation.
operation-name
The operation name. For example, "child".
average-duration-ms
The average duration of the operation.
average-size
The average result size of the operation.
unique-caller-count
The number of unique executions of the identified operation. This number is usually a fraction of the call-count value. For instance, in this sample, out of 20 execution of the operation, 4 of executions used a unique combination of key and value parameters. This number means that 16 executions could potentially result in cache hits.

Sample

The following code is a sample caller report.
<caller call-count="20" average-call-count="1.00" operation-name="child">
<caller call-count="10" average-call-count="1.00" operation-name="parent-1" />
<caller call-count="5" average-call-count="2.00" operation-name="parent-2" />
</caller>
This sample identifies that the following operation calls occurred:
  • The "child" operation was called 20 times in total.
  • The "child" operation was called 10 times by the operation "parent-1" with a relationship of 1 to 1.
  • The "child" operation was called 10 times by the operation "parent-2" with a relationship of 2 to 1. This result means that on average, each execution of the "parent-2" operation resulted in 2 executions of the "child" operation.