Philip Martin <phi...@codematters.co.uk> writes: > Here are the cache stats before/after a run once the timing has > stabilised: > > gets : 11770766, 4388248 hits (37.28%) > sets : 7309448 (99.01% of misses) > failures: 0 > used : 777 MB (94.56%) of 822 MB data cache / 958 MB total cache memory > 2225228 entries (99.45%) of 2237592 total > > gets : 12914318, 4814238 hits (37.28%) > sets : 8019703 (99.01% of misses) > failures: 0 > used : 778 MB (94.69%) of 822 MB data cache / 958 MB total cache memory > 2229936 entries (99.66%) of 2237592 total
Note how the sets goes up, that means each run is getting cache misses that lead to sets. In contrast, 1.9 sees no increase in sets after the first run, so eveything is found in the cache and the hits percentage gradually increases towards 100%. So 1.11 is faster than 1.9 even though 1.11 seems to fail to caching everything. -- Philip
