median is probably also useful. I like it a little better in cases where the code being tested triggers gc() more than half the time.
On Monday, June 2, 2014, Steven G. Johnson <[email protected]> wrote: > > > On Monday, June 2, 2014 1:01:25 AM UTC-4, Jameson wrote: >> >> Therefore, for benchmarks, you should execute your code in a loop enough >> times that the measurement error (of the hardware and OS) is not too >> significant. >> > > You can also often benchmark multiple times and take the minimum (not the > mean!) time for reasonable results with fairly small time intervals. >
