News #16:
Go exhibited some of the highest variance during cold starts (initial runs could take 69 ms, dropping and stabilizing to 50 ms when repeated). I stabilized the benchmarks by introducing a warm-up phase before taking measurements. The results are now highly accurate and consistent.
I added further optimizations (I am currently working on a Worker/Wrapper pattern, to shave off the last few microseconds).
It’s completely trivial now, but still… I have to say: what follows really made me happy…
Go has overtaken Scheme for the first time, since I started working on gopurs a month ago.
It now ranks first among the backends tested in the benchmark. (In reality, fluctuations after the decimal point make the match very close on my local machine. But hey, I’m still really happy about it.)
Go:
Scheme:
