CPU time measures how long a method actively uses the processor to execute instructions. Compare it with total execution time when investigating latency. section 6.1
Use CPU time to guide performance diagnosis:
- High CPU time indicates that the method is doing work; reducing algorithmic complexity may improve performance. section 6.1
- Low CPU time combined with long execution time indicates waiting, such as for an HTTP response. section 6.1
- Profiler stacks include application methods and dependency methods, helping locate work or waiting across the call path. section 6.1
Five-second HTTP delay
A /demo endpoint takes about five seconds because getResponseCode() waits for an HTTP response. Its CPU time is zero, so the application is waiting rather than consuming processor resources. section 6.1
