Great write-up. I've done countless investigations like this and couldn't have worded it better. >Depth vs. breadth. Ah yes, which direction do you look at yo

Great write-up. I've done countless investigations like this and couldn't have worded it better. >Depth vs. breadth. Ah yes, which direction do you look at your program? do you look at which functions consume the most resources bottom up (probably some string or memory function in libc) or top down? If you're the person writing the system libraries for enormous platforms, probably bottom-up, but if you're an application developer, top down. Sometimes though, especially with the performance issue described in the article you're in the middle -- those are tough to spot!