I don’t know if it will help his particular case but there has been
significant performance work, and much still to come, that has a
dramatic effect on the performance of some benchmarks like this. Even
what’s at tip now is much faster than go1.0.2 because of changes to
the compiler and run-time.
Leaving aside the general unreliability of benchmarks.
Rob Pike’s answer on topic. (via golang-nuts)