i am still confused about cache footprint.
"cache footprint can be thought of as the amount of cache that improves performance by enabling fast data
reuse within the program."
what is the mean of small or largecache footprint ?
Could you take a specific example in multi-core architecture?
I think it is best to leave out running several programs for a moment. Let us consider only one process and consider a system where the last level cache is shared. For the "cache footprint" it is then not important if the process uses one or several threads. Vaguely speaking, the cache footprint tells you how large the cache needs to be for the application to run smoothly.
If you assume that you could change the cache size of theprocessor by disabling parts ofcache or adding more cache, the cache footprint then corresponds to the size where adding more cache does not improve the performance anymore. An application with a small cache footprint cannot take advantage of a large cache; an application witha large cache footprint won't perform on a processor with small cache.
With this in mind, I think Robert's explanation captures very well what the cache footprint is and what its implications are.
thank you for Thomas Willhalm and Robert 's excellent explantation.
i am a student and have been studying on cache tuning .
i am lack of further understanding on cache principle.so i could be confused about your explantation.
i will continue to be studying for this aspect.