Service analysis operates with many different timings, describing the behavior of the service. The table below provides an overview of such timings. Timings vary in different analysis types:
Regardless of which analysis you're running, it is not guaranteed that you'll see all of the timings listed here. The actual timings you see depend completely on how you're running your services. For example, if the distributed trace runs completely on one host without any networking involved, you won't see any network-related times.
Time
Appears in
Description
Response time
DT
SF
The total execution time of the first node of a distributed trace.
Response time
RT
The total execution time of the method.
Processing time
DT
RT
The duration of the distributed trace from start to end.
It is the wall-clock time (difference between start and end time), not the sum of all asynchronous executions.
Execution time
RT
The total time taken to execute the code.
It is the sum of all asynchronous executions, so it might be longer than the processing time.
Suspension
DT
RT
The time during which any code execution is halted. It is usually caused by garbage collection.
Wait time
DT
The time during which the code actively waits for something (for example, Object.wait() or a similar functionality).