Lecture 24: High Performance Image Processing & Halide (57)
JerryJiehanWang
I don't quite understand why higher locality means more redundant work? For example, can't we just calculate a row and keep them inside memory for future use?
Staffrishiu
Someone correct me if I'm wrong, but I think the issue with that may be that storing the values for every position could get very storage-expensive very quickly and the extra memory access could affect the speed.
afang-story
To add on to the above, there is a hierarchy of memory and the fastest ways of accessing memory are at the level where the size is smaller.
kavimehta
I agree with the above. Storing a row of data in memory would quickly become cumbersome
I don't quite understand why higher locality means more redundant work? For example, can't we just calculate a row and keep them inside memory for future use?
Someone correct me if I'm wrong, but I think the issue with that may be that storing the values for every position could get very storage-expensive very quickly and the extra memory access could affect the speed.
To add on to the above, there is a hierarchy of memory and the fastest ways of accessing memory are at the level where the size is smaller.
I agree with the above. Storing a row of data in memory would quickly become cumbersome