profiling for where time is being spent is something that pretty much every developer wants to do at some point from the very first programs you're writing. But looking at where your program is spending memory is more of a special case that only comes up in either when you have a program that's using too much memory and you need to figure out how to pair it back, or if you are trying to optimize an entire suite of applications running on one set of boxes. "Memory has this funny thing compared with time," he says. When people think about the time my program is spending on something, they really know what they are talking about. They know what you want.