I haven't dug into this example myself, but all those allocations are worrying. Seems like something might have regressed; hopefully the fix will not be difficult. This is one of the downsides of having threading off by default.
I'd recommend filing an issue about it. Best, --Tim On Friday, March 04, 2016 09:19:17 PM [email protected] wrote: > Dear Sam, > the output of the benchmark is following > > 105.290122 seconds (31.43 k allocations: 1.442 MB, 0.00% gc time) > 107.445101 seconds (1.37 M allocations: 251.368 MB, 0.12% gc time) > > Tomas
