3 ms·
I think most people would measure instructions per cycle as an estimate of how busy the CPU execution units actually are. Lots of performance tools do measure i
by grogers 3y ago
I think most people would measure instructions per cycle as an estimate of how busy the CPU execution units actually are. Lots of performance tools do measure it.
- dist1ll 3y agoIPC is not a good performance metric - especially for an instruction set like x86, but particularly for SIMD ISAs. Two seemingly similar instructions sequences may get decoded into a different number of uops, which in turn occupy different execution ports. The most extreme example of this being scalar code without stalls. It tends to have high IPC, even though it makes no use of FP/SIMD ports. Keeping the execution pipeline busy is not a useful goal in isolation. Really, IPC is better left as a sanity check.