The combined read/write miss per memory operation of 11.6% is accurate. That 11.6% also includes the MEMORY PERFORMANCE tests (memcpy, memset and lots of Streams variants) which have a 100% miss rate. Maybe I should invest the time to grab the information before the memory tests start. Note that the miss rate was from gb version 3.1.5
Interestingly, most of the "studies" on SPEC use the metric MISSES PER 1000 INSTRUCTIONS which is different than MISSES PER MEMORY ACCESS. I will have to be careful to identify which. From memory, there is typically 0.3 memory reads per instruction and
I have a copy of geekbench2 2.3.4 and there is an undocumented geekbench option where you can run just a single workload. That makes it easier to grab the per workload metrics. It does not appear to work the same (or possibly at all) on geekbench 3.
For example, if you add "--workload 101" to the geekbench 2 run, it will only run the Blowfish benchmark ....