MOHD AFIF BIN MD NASIR831011-01-5687M031010028

Project 2: Influence of the Cache Size

Hydro

Hydro 1

Hydro, block in cache (1)

Hydro 2

Hydro, block in cache (2)

Hydro 4

Hydro, block in cache (4)

Hydro 8

Hydro, block in cache (8)

Hydro 16

Hydro, block in cache (16)

Hydro 32

Hydro, block in cache (32)

Hydro 64

Hydro, block in cache (64)

Hydro 128

Hydro, block in cache (128)

Hydro 256

Hydro, block in cache (256)

Hydro 512

Hydro, block in cache (512)

Nasa7 1

Nasa7, block in cache (1)

Nasa7 2

Nasa7, block in cache (2)

Nasa7 4

Nasa7, block in cache (4)

Nasa7 8

Nasa7, block in cache (8)

Nasa7 16

Nasa7, block in cache (16)

Nasa7 32

Nasa7, block in cache (32)

Nasa7 64

Nasa7, block in cache (64)

Nasa7 128

Nasa7, block in cache (128)

Nasa7 256

Nasa7, block in cache (256)

Nasa7 512

Nasa7, block in cache (512)

Cexp, block in cache (1)

Cexp, block in cache (2)

Cexp, block in cache (4)

Cexp, block in cache (8)

Cexp, block in cache (16)

Cexp, block in cache (32)

Cexp, block in cache (64)

Cexp, block in cache (128)

Cexp, block in cache (256)

Cexp, block in cache (512)

Mdljr, block in cache (1)

Mdljr, block in cache (2)

Mdljr, block in cache (4)

Mdljr, block in cache (8)

Mdljr, block in cache (16)

Mdljr, block in cache (32)

Mdljr, block in cache (64)

Mdljr, block in cache (128)

Mdljr, block in cache (256)

Mdljr, block in cache (512)

Ear, block in cache (1)

Ear, block in cache (2)

Ear, block in cache (4)

Ear, block in cache (8)

Ear, block in cache (16)

Ear, block in cache (32)

Ear, block in cache (64)

Ear, block in cache (128)

Ear, block in cache (256)

Ear, block in cache (512)

Comp, block in cache (1)

Comp, block in cache (2)

Comp, block in cache (4)

Comp, block in cache (8)

Comp, block in cache (16)

Comp, block in cache (32)

Comp, block in cache (64)

Comp, block in cache (128)

Comp, block in cache (256)

Comp, block in cache (512)

Wave, block in cache (1)

Wave, block in cache (2)

Wave, block in cache (4)

Wave, block in cache (8)

Wave, block in cache (16)

Wave, block in cache (32)

Wave, block in cache (64)

Wave, block in cache (128)

Wave, block in cache (256)

Wave, block in cache (512)

Swm, block in cache (1)

Swm, block in cache (2)

Swm, block in cache (4)

Swm, block in cache (8)

Swm, block in cache (16)

Swm, block in cache (32)

Swm, block in cache (64)

Swm, block in cache (128)

Swm, block in cache (256)

Swm, block in cache (512)

UComp, block in cache (1)

UComp, block in cache (2)

UComp, block in cache (4)

UComp, block in cache (8)

UComp, block in cache (16)

UComp, block in cache (32)

UComp, block in cache (64)

UComp, block in cache (128)

UComp, block in cache (256)

UComp, block in cache (512)

INFLUENCE OF THE CACHE SIZE Answer from Project 2 questions

- The degree of misses decreases when increasing the cache size because more data can be stored into the cache at the same time

- Degree of misses decreases on all trace files

- With the increasing cache size the effectiveness raises up to approximately 90% hits, after that increasing the cache size is hardly the way of increasing effectiveness

- Yes, there are conflict (collision) misses in this experiment and they occur when another location with the same mapping was loaded (can also be considered associativity capacity)

- At large cache size the degree of misses stabilizes because of the “Compulsory misses” - Compulsory misses are those misses caused by the first reference to a datum. As cache grows, compulsory misses increase in proportion to other types because capacity misses decrease (Improving overall cache performance doesn't result from focusing on just one type of miss).

- The more cache the system has, the more likely it is to register a hit on a memory access, because fewer memory locations are forced to share the same cache line

- They happen when we first double the cache

- The degree of misses has decreased when increasing the block size because in this way we increase the number of words(data) in each block of the cache and also because of the spatial locality since the probability, in near future, for accessing close data to the accessed words increases.

CONCLUSION

Yes, there is an efficiency improvement with the increasement of the size but only up to a point.