in reply to Re^3: code optimization
in thread code optimization
Profilers can lead to false optimizations because your measuring the overhead of recording the timings (OS interrupts/OS calls/context switches/mutex hits/evals/method resolution) or 1 run if the func is below the OS timer resolution. I took nytprof to these subs and nytprof changed which is the fastest sub which is no good.
Well, Benchmark isn't exactly a profiler, and reinventing Benchmark seems like a particularly pedestrian thing to reinvent, and the overhead is accounted for
But, regarding NYTProf, I don't get the argument, its not as if it is Benchmark :)