3 ms·
The problem with these benchmarks is they measure the bandwidth you can push through an established tls connection. Try to build 2000 new tls connections a seco
by tpetry 5y ago
The problem with these benchmarks is they measure the bandwidth you can push through an established tls connection. Try to build 2000 new tls connections a seconds (yes many are still active and dont need to be restarted) that is what is the really slow part. Not sending the data over already established channels.
- lossolo 5y agoThis exactly. Most CPU time in our Haproxy is spent on crypto/new TLS sessions handling thousands of new connections per second.