5 ms·
I would also like to see benchmarks for reverse proxies with TLS termination.
by fullstop 4y ago
I would also like to see benchmarks for reverse proxies with TLS termination.
- capableweb 4y agoYeah, this tends to be (in my cases) where response times suffer the most, unless your bottleneck is I/O to/from the backend or further away
- mholt 4y agoI think one reason a lot of benchmarks don't include TLS termination is because it's often impractical in the real-world, where most clients reuse the connection and the TLS session for many requests, thus making them negligible in the long run. And given hardware optimizations for cryptographic functions combined with network round trips, you end up benchmarking the network and the protocol more than its actual implementation, which is often upstream from the server itself anyway. Go's TLS stack is set to be more efficient and safer in coming versions thanks to continued work by Filippo and team.
- nerdponx 4y agoMaybe it would be a useful benchmark to simulate a scenario like "my site got posted on HN and now I'm getting a huge number of unique page views."
- mholt 4y agoSure, we've already done this very real test in production a number of times and Caddy doesn't even skip a beat. (IMO that's the best kind of benchmark right there. No need to simulate with pretend traffic!)
- CoolCold 4y agoAny idea on how much traffic could be from HN? I doubt more than 100 rps or any other noticeable load
- porker 4y agoh2o [1] was excellent when I tried it for TLS termination, beating hitch in my unscientific tests. And it got http/2 priorities right. It's a shame they don't make regular releases. 1. https://github.com/h2o/h2o/ https://github.com/h2o/h2o/