3 ms·

I believe the problem described in this blog has been at least partially addressed in the Go 1.12 release.