Genuinely curious, are there any cases of production Go environments where routing is the bottleneck of their HTTP services? I'd think any kind of data access in the service would be the bottleneck, not routing.
Silly question, but where's the "plain net/http" benchmark? I haven't found a case where I've missed having an http framework.<p>Would be interesting to see what the baseline is.
I know this is a dumb question, but is there a conclusion to the benchmarks that which one would be more ideal to use?<p>I'm just learning GO, that is why I'm asking.