https://youtu.be/DJ4d_PZ6Gns?t=535 ( it's one of the best Go performance video on Youtube )
One example is high-performance routing on 10Gbps networks using user-space networking. Pretty much every cycle counts into your throughput numbers, because the rest of the hardware can barely keep up with the network card even before you're trying to do something. Go is a poor fit for this use case.
(This from someone who has been accused of being a Go shill. I use it a lot and like it a lot professionally, but it is no more suitable for every task than any other language.)
There are large scale online services ( in the millions req/sec ) that runs on Go without problems.
just spawn goroutines that select on the (optionally buffered) channel
if you need to fan out even further, repeat this on the spawned routines
That's all relative. There are legitimate reasons to trade a bit of complexity for a bit of speed. Go is not special in this regard.
One challenge of writing this kind of code in go is that go routines are not pre-emptive, so you can't just port over an implementation that works in c.