[sldev] https very slow.

[Tateru Nino]

https defaults to connection re-use (and may in some circumstances, also
pipeline, though true pipelining - that is multiple outstanding requests
on the same connection- is rare). The reason that it's sometimes slower
when viewing websites is that most browsers do not parallelize https
connections to a server, but instead waits for responses on the pipe
before issuing further requests. That said, the slowdowns of this
approach are significantly mitgated by the widening of the TCP window
after a couple of entities have transferred.

Matthew Dowd wrote:
>  
>   
>> 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.
>>     
>
> My understanding of http pipelining is that in the latter situation (lots of events coming in over CAPS) you could still use the same https connection and not have to set up and tear down https connections in that scenario. Sorry, I've not delved into CAPS enough to know if that scenario is particularly likely and whether using http pipelining would be an optimisation or a case of diminishing returns.
>
> Matthew
> _________________________________________________________________
> 100’s of Music vouchers to be won with MSN Music
> https://www.musicmashup.co.uk/index.html_______________________________________________
> Click here to unsubscribe or manage your list subscription:
> /index.html
>
>   

-- 
Tateru Nino
http://dwellonit.blogspot.com/