in reply to Re^2: What is the best way to compare profiling results before and after a code change?
in thread What is the best way to compare profiling results before and after a code change?

To deal with that, I usually run the thing I'm profiling a few times in order to average out the differences. It's not practical with really large programs, but when possible I'll do 10 runs while recording profile data. That tends to smooth things out.
  • Comment on Re^3: What is the best way to compare profiling results before and after a code change?