Same loop, same data — different order, brutal gap
This cache display groups four adjacent cells in each row into one assigned cache line. In the default eight by eight grid there are sixty-four cells and sixteen distinct line keys. The first visit to each line is a miss; the remaining forty-eight visits are hits. Bars show sixteen misses and forty-eight hits at ten pixels per access. These counts follow the written row times ceiling of N over four plus floor of column over four key formula, not hardware measurement. The simulator assigns ten stall cycles to a miss and one cycle to a hit. For an eight by eight complete traversal, sixteen misses contribute one hundred sixty cycles, and forty-eight hits contribute forty-eight cycles. Both bars show assigned cycle contributions at three pixels per cycle; the total is two hundred eight. These are invented teaching costs, not a benchmark, clock timing or a processor latency specification. The page retains every loaded line in an unbounded Map until resetting; it never evicts. Both row-major and column-major therefore eventually visit the same sixteen distinct keys, producing the same two hundred eight assigned cycles in this saved implementation. Bars have identical lengths at two pixels per cycle. The source heading suggests a column-major slowdown, but its current cache model cannot demonstrate that cost difference. Preserve the limitation instead of inventing a speedup or changing the original tool.