std.benchmark is in reviewable state

[Jens Mueller]

Andrei Alexandrescu wrote:
> On 9/25/11 11:56 PM, Robert Jacques wrote:
> >On Sun, 25 Sep 2011 23:06:01 -0400, Andrei Alexandrescu
> ><SeeWebsiteForEmail at erdani.org> wrote:
> >>>So, std.benchmark should
> >>>[ ] Set the affinity to a single thread at start (i.e. use
> >>>SetProcessAffinityMask, etc)
> >>
> >>I think that won't influence most measurements measurably.
> >
> >First, a core jump is guaranteed to, essentially, poison the cache.
> >Which, at least in my eyes, invalidates that particular timing run.
> 
> Well it will be one of many runs. The questions are if (a) core
> jumps are likely to happen during a benchmark run, (b) many enough
> will happen to influence a 500ms time window.

500?
To me it looks as if the time window is 10ms long (line 447)?

Jens