3 ms·
From reading the recent 'ImperialViolet' article titled 'Overclocking SSL' about Google's efforts, it seems the issues are that: - unless you use the recently
by gojomo 16y ago
From reading the recent 'ImperialViolet' article titled 'Overclocking SSL' about Google's efforts, it seems the issues are that:
- unless you use the recently patched version, OpenSSL uses an overhead of 50KB per connection; even with the patch, it's 5KB. (It's not clear if this 'connection' overhead is also the size of the 'session' data which must be cached for followup handshakes to go faster.)
- in all cases using commonly-available software, SSL adds roundtrips to connection-establishment, and thus latency for the end-user. Minimizing this requires carefully choosing how you handle certificates and how you cache session info, and having a large or shared session cache may need different load-balancing than sites already use.
- Google has several proposals (all dated 2010) for further reducing or in some cases eliminating roundtrips; no implementations other than in Google Chrome and Google's frontend servers were mentioned by the 'Overclocking' article.
So there's still an adjustment cost, new overhead costs, and a latency cost, for adopting SSL. You can minimize these by doing-as-Google-does, but the software to do so is not yet freely available.
- tav 16y agohttp://github.com/downloads/tav/ampify/distfile.openssl-0.9.8o.tar.bz2 http://github.com/downloads/tav/ampify/distfile.openssl-0.9.... ^ Patched version of OpenSSL for the various optimisations...
- jrockway 16y agoAh, patched versions of OpenSSL. Those never cause problems...
- rarrrrrr 16y agoSpiderOak has always been an all-SSL site, for all services (including data storage and retrieval.) We've found the Erlang implementation of SSL scales more comfortably than OpenSSL. (The new Erlang implementation, available since r12, and the default in r14, isn't just a wrapper for OpenSSL.)