Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Apart from those, there's all sorts of rankings at https://www.techempower.com/benchmarks to ogle at, but these are potentially gamed benchmarks, and they may not map to your specific situation (especially: making sure your code isn't the bottleneck). Maybe swapping around the HTTP handling code will net a benefit, but, depending on how much real work the application is doing, maybe it's just not going to save a lot. E.g.: if a typical request takes 4ms to put together due to a couple microservice calls, and you're spending 500 microseconds of that in stdlib HTTP: how much better are things if you somehow magically get a 10x faster HTTP implementation?
Google's solution to this is QUIC. There's a few implementations in Go (e.g.).
https://github.com/acln0/zerocopy perhaps this can speed things up further by removing some memory allocs in go itself ?