On: CPU Utilization is Wrong

[westurner]

Instructions per cycle: https://en.wikipedia.org/wiki/Instructions_per_cycle

What does IPC tell me about where my code could/should be async so that it's not stalled waiting for IO? Is combined IO rate a useful metric for this?

There's an interesting "Cost per GFLOPs" table here: https://en.wikipedia.org/wiki/FLOPS

Btw these are great, thanks: http://www.brendangregg.com/linuxperf.html

( I still couldn't fill this out if I tried: http://www.brendangregg.com/blog/2014-08-23/linux-perf-tools... )

[gefh → westurner]

It's not that your code should be async, but that it should be more cache-friendly. It's probably mostly stalled waiting for RAM.

[westurner → gefh]

Oh, is this because of context switching for resource staring?

[adrianN → westurner]

http://stackoverflow.com/questions/16699247/what-is-cache-fr...