3 ms·
Yeah, so now you're basically running a heavy instance in order to get the network throughput and the RAM, but not really using that much CPU when you could pro
by tcdent 1y ago
Yeah, so now you're basically running a heavy instance in order to get the network throughput and the RAM, but not really using that much CPU when you could probably handle the encode with the available headroom. Although the article lists TLS handshakes as being a significant source of CPU usage, I must be missing something because I don't see how that is anywhere near the top of the constraints of a system like this.
Regardless, I enjoyed the article and I appreciate that people are still finding ways to build systems tailored to their workflows.
- inlined 1y agoMaybe they’re not using keepalives in their clients causing thousands of handshakes per second?
- ruperthair 1y agoYes, they mention this as a 'fix' for connection-related memory usage: > Disable keep-alive: close the connection immediately after each upload completes. Very odd idea.
- kevin_thibedeau 1y agoPossibly missing session resumption support compounding the problem.
- ahoka 1y agoTLS being a bottleneck when doing image processing is very-very weird.
- mannyv 1y agoThey should terminate TLS at the LB and use normal connection inside...unless they have some HIPAA privacy-like regulation going on.