W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2007

Re: pipelined client/server behaviour

From: Adrien de Croy <adrien@qbik.com>
Date: Mon, 02 Apr 2007 00:09:33 +1200
Message-ID: <460FA0FD.8050405@qbik.com>
To: Adrian Chadd <adrian@creative.net.au>
CC: ietf-http-wg@w3.org



Adrian Chadd wrote:
> On Sun, Apr 01, 2007, Adrien de Croy wrote:
>   
>> The worse aspect kicked in once servers started dropping connections 
>> when they got a pipelined request.  Rather a negative impact on 
>> performance that one, esp with connection-based authentication.
>>
>> So overall statistically we saw it as worse, and the benefit on the 
>> sites that supported it seemed very small as well.  You're only talking 
>> about saving one RTTs per request to send requests serialized (after 
>> response received) than pipelined.  The biggest performance improvement 
>> we saw in testing came about from the reuse of the connection.
>>
>> I guess if all servers and intermediaries supported pipelining, it would 
>> perform better overall, but I don't think it's widespread enough yet, so 
>> we decided to trade a small performance loss for an improvement in 
>> stability and ease of implementation.  We may still revert on this.
>>     
>
> Did you benchmark it over higher latency links? It might not give great
> performance boosts for under 100ms but anecdotally it seems to load
> pages in Mozilla faster when the site RTT is ~300 to ~400ms (think
> .eu site accessing .au, or vice versa.)
>
>
>   

I'll have to check that - no is the likely answer though - good point re 
the latency. thanks.

Adrien


>
> Adrian
>
>   
Received on Sunday, 1 April 2007 12:11:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:50:09 GMT