Re:A cache miss is not a cache miss
by onetimePete on Sunday May 01, 2016 @11:51AM
(#11606630)
So you suggest cache misses corrected by a instruction-workload bias (which should be again biased by how "hot" the instructions remain)?
EvilOfCacheMiss = TimeOfMemoryFetchCycles - CyclesSpendDoingInstructions /TimeOfMemoryFetchCycles
More like TimeOfMemoryFetchInCycle - CyclesSpentDoingInstructions
But yeah, sounds like a useful metric to me.
This discussion reminded me of a formula for calculating the average cost of a cache miss in this pretty cool paper ("An Analysis of the Effects of Miss Clustering
on the Cost of a Cache Miss").
In particular, see Equation 4: http://researcher.ibm.com/files/us-viji/miss-cluster.pdf
As long as we don't have that, cache misses are a useful metric on their own, as long as one is aware of its caveats. As most things, cache misses come in various shades of grey.