3 ms·
The overhead can be minimized on subsequent connections if you pin a client to one server handling TLS termination for the session (you can either pin to one ap
by snuxoll 10y ago
The overhead can be minimized on subsequent connections if you pin a client to one server handling TLS termination for the session (you can either pin to one application server, or a specific load balancer) and your servers have enough memory to keep an adequate number of sessions in memory. You probably take up roughly 10KB of memory per TLS session that's active, so 100 active sessions per 1MB or so which isn't too bad.
- umanwizard 10y ago> subsequent connections What if most of your users are first-time visitors coming from google results?
- snuxoll 10y agoYou take an extra hit the first time a TLS session key is established, after that all subsequent HTTP requests can do a fast resume. This has nothing to do with users over a period of time.