Using Blocking to Increase Temporal Locality

In the last essay Rearranging Loops to Increase Spatial Localitywe saw how some
simple rearrangements of the loops could increase spatial locality. But observe that even with good loop nestings, the time per loop iteration increases with increasing array size. What is happening is that as the array size increases, the temporal locality
decreases, and the cache experiences an increasing number of capacity misses. To fix this, we can use a general technique called blocking.

The general idea of blocking is to organize the data structures in a program into large chunks called blocks. (In this context, the term “block” refers to an application-level chunk of data,
not a cache block.) The program is structured so that it loads a chunk into the L1 cache, does all the reads and writes that it needs to on that chunk, then discards the chunk, loads in the next chunk, and so on.

Blocking a matrix multiply routine works by partitioning the matrices into submatrices and then exploiting the mathematical fact that these submatrices can be manipulated just like scalars.
For example, if n = 8, then we could partition each matrix into four 4×4 submatrices:

The version of blocked matrix multiplication, which we call the bijk version is presented below. The basic idea behind this code is to partition A and C into 1×bsize
row slivers and to partition B into bsize×bsize blocks. The innermost (j, k) loop pair multiplies
a sliver of A by a block of B and accumulates the result into a sliver of C. The i loop iterates through n row slivers of A
and C, using the same block in B.

The key idea is that it loads a block of B into the cache, uses it up, and then discards it. References to A enjoy good spatial locality
because each sliver is accessed with a stride of 1. There is also good temporal locality because the entire sliver is referenced bsize times in succession. References to B enjoy good temporal locality because the entire bsize×bsize
block is accessed n times in succession. Finally, the references to
C have good spatial locality because each element of the sliver is written in succession. Notice that references to C do not have
good temporal locality because each sliver is only accessed one time.

Blocking can make code harder to read, but it can also pay big performance dividends. Blocking improves the running time by a factor of two over the best non-blocked version, from about 20 cycles
per iteration down to about 10 cycles per iteration.