3 ms·
I wonder what is causing the bottleneck in the TLS case, particularly with kTLS where the CPU is only at 2% but the throughput remained the same. Perhaps there
by zamadatix 5y ago
I wonder what is causing the bottleneck in the TLS case, particularly with kTLS where the CPU is only at 2% but the throughput remained the same. Perhaps there is a limited size stream buffer somewhere in the crypto side that doesn't allow high throughputs whereas the raw networking buffers are more dynamic? I know the Caddy guys read HN so maybe they can chime in with some actual knowledge :).
- Matthias247 5y agoIt might have maxed out the CPU core on the peer/client? There's no mention of what it's CPU usage is.
- secure 5y agoNo, it didn’t max out CPU (not even a single core) on either of the machines. My theory is that you only have a limited time window per TCP packet, and decrypting TLS exceeds that time window. I haven’t verified that theory yet, though.