News for hackers. Stuff that matters.
Re:Go 1.9 is released by to3m on Friday August 25, 2017 @09:58AM (#15098429)
If the measurements are all over the place, why not take the fastest? The average is no good, because it'll be influenced by the times it wasn't running as fast as possible.

I don't myself lose much sleep over worrying about the times it runs faster than possible.

Re:Go 1.9 is released by fnord123 on Saturday August 26, 2017 @07:14AM (#15104982)
I agree with this sentiment. Any time worse than the fastest is due to noise in the system (schedulers etc). So the fastest is the lowest noise run.

Of course, as I said in another comment it depends what you want to do with the measurement. If you plan to edit how long a run will take on an existing system, then you need to accept the noise and use the mean (or median).