[sldev] https very slow.

John Hurliman jhurliman at wsu.edu
Wed Jul 11 01:28:05 PDT 2007


Matthew Dowd wrote:
> May not be routing. It could be some hiccup or timeout doing the certificate chain validation and/or attempting to retrieve certificate revocation lists.
>
> https is always slower than http due to the overhead of setting up the encryption each request: quite a lot of sites which don't dealing with confidential information (so for instance wikis, message boards, etc.) use https just for the authentication step (to protect username and password) and/or signup process but then drop to http. The difference between https and http is particularly noticeable if you are doing a lot of small requests in quick succession (each involving setting up and taking down the encryption stack), so even https enabling websites may use http for static images (especially if they have a lot of small icons).
>
> Another solution is to use http pipeling (http://en.wikipedia.org/wiki/HTTP_pipelining) so that you only set up the encrytion stack once and send all the requests and responses over the same connection - does the SL caps stuff use this?
>
> Matthew
>   

CAPS holds connections from the client to the server open until the 
server has something to say, or the connection times out. After either 
case the connection is immediately re-established, so you are only 
setting up and tearing down https connections if there are a lot of 
events coming over CAPS.

John Hurliman


More information about the SLDev mailing list