> in order to justify not using a profiler, when profiling is such a simple and easy thing. My day job is basically performance optimization. It is not simple

> in order to justify not using a profiler, when profiling is such a simple and easy thing. My day job is basically performance optimization. It is not simple nor is it easy to use a profiler. In fact, profilers often don't tell you anything useful at all. They'll tell you sort of where you're spending your time, but they don't help at all in telling you why you're spending your time there. Most of the major performance wins I find are from optimizing the architecture not from optimizing a hot loop. I can't even think of the last time I've seen any measureable difference from optimizing a hot loop. Heck, I can't even remember the last time I found a hot loop. Then again I work on things more like game engines and web browsers. Huge systems with tens of thousands of lines of code on the hot path. Profilers don't help all that much here, and I can optimize in advance in less time than it'll take to setup the profiler and "justify" the change.