Kurt Stephens wrote:
> Looks like GC overhead/interaction was the culprit.  Note to self,
> remember to disable GC around benchmarks :(.

A benchmark that doesn't consider GC is a bad benchmark. Don't disable 
it; expect it.

- Charlie