I have not attempted to reproduce yet, but if a couple of these are the functions I think they are, these are pretty alarming!
time.Now() is something I know my applications have the potential to call very heavily, from setting net.Conn deadlines to calculating evetive dates from TTLs....
/localdisk/itocar/golang/src/time/Now-6                                                                36.4ns ± 0%    72.8ns ± 1%  +99.93% (p=0.000 n=8+8)
/localdisk/itocar/golang/src/time/NowUnixNano-6                                                        37.5ns ± 0%    74.9ns ± 1%  +99.73% (p=0.000 n=8+8)
This could be a pretty dramatic increase in garbage generation for anything that is a public facing HTTPS server right?
/localdisk/itocar/golang/src/net/http/ClientServerParallelTLS4-6                                       4.97kB ± 0%   24.61kB ± 3% +395.20% (p=0.000 n=8+7)
/localdisk/itocar/golang/src/net/http/ClientServerParallelTLS4-6                                         64.0 ± 0%     258.3 ± 3% +303.57% (p=0.000 n=8+7)
Before my team adopts 1.9 we will have to run these tests on our prod HW and bench our apps, but at a glance the items above are a bit concerning.
What happened here?
/localdisk/itocar/golang/src/net/http/ClientServerParallelTLS64 126µs ± 2% 1800µs ±16% +1333.24% (p=0.000 n=8+8)
/localdisk/itocar/golang/src/net/http/ClientServerParallelTLS64 5.37kB ± 0% 60.32kB ±13% +1022.65% (p=0.000 n=7+8)