Measuring what code is idling and how long.

[Javier S. <jsc...@gm...>]

Hi,

Does OProfile provide any way to include code that is idle in the call
graphs? So that, for example, if a function spends 4 seconds in a
sleep(4) call, and another function spends 4 seconds on real
calculations (CPU time), both would be shown in the same position of
the reports. That way OProfile could also be used when profiling
systems where the bottleneck is not the CPU, but disk IO, network IO,
or lock contention.

Particularly it's lock contention what I'm after. If OProfile cannot
measure this, any suggestion better than taking random call stack
snapshots with gdb would be appreciated.

Thanks,
    Javier