At scale, it seemed the largest part of the complexity of go was manipulating data structures and code to avoid gc pauses. With sufficient work we may have been able to decrease the pauses sufficiently, but we also ran into raw request per second numbers that were lower than we liked.
The direction we have taken was to switch to C++ for this application. Having said that, the gc pauses were the primary reason for the change.
If you've got a C++ solution, I would not suggest under any circumstances short of Go suddenly and frankly mysteriously blowing the doors off of C++ that you switch... I'm just saying it would be an interesting comparison.
It's about 0.3ms per MB, so 1ms isn't that different.
Though admittedly, some of these have a dismal concurrency story so I got to hand Go credit where it deserves.
Looks like they are tackling this head on with positive results.