concept memory footprint in category software development

appears as: memory footprint, memory footprint
Seriously Good Software: Code that works, survives, and wins

This is an excerpt from Manning's book Seriously Good Software: Code that works, survives, and wins.

In this chapter, assume your water-management program will deal with millions, perhaps even billions of containers, and you want to keep as many of them as possible in main memory. Clearly, you’ll want to shrink the memory footprint of each container as much as possible. On the other hand, you don’t need to worry about the memory that temporary local variables use because they live only the short time span of a method call.

3. The values of the indices have no effect on the structure of a SparseArray. That’s exactly the meaning of “sparse” in its name. As a result, the memory footprint in this scenario is the same as in question 2: 857 bytes.