Wall-clock profiling measures elapsed time while a thread runs or waits. It exposes delays hidden from CPU profiles, including lock contention, database waits, and external service calls. section 7.2.3
Use it when endpoint latency exceeds what CPU activity explains:
- Profile CPU time first and inspect the flame graph. section 7.2.3
- Switch to wall-clock mode when the profile looks clean but the endpoint remains slow. section 7.2.3
- Compare the result with request timing logs to locate the hidden waiting phase. section 7.2.3
A slow API with a clean flame graph
An endpoint may spend little CPU time while waiting on a lock, database connection, or external service. Wall-clock profiling makes that blocked interval visible and directs investigation toward the actual latency source. section 7.2.3
