Alternate robust performance measures other than running time

As many users have realized, the run-times for the same algorithm usually vary from execution to execution. It would be nice to see the alternative measures of performance, e.g. number of instructions executed, cache hits and misses etc. This would provide a more robust performance measure along with other interesting metrics. Integrating profiling with tools like valgrind could provide such metrics.
I would like to hear what you think.

Comments (1)