W3C home > Mailing lists > Public > www-talk@w3.org > September to October 2000

Re: Persistant connections and pipelining...

From: Yves Lafon <ylafon@w3.org>
Date: Wed, 25 Oct 2000 21:22:28 +0200 (MET DST)
To: Reinier Post <rp@win.tue.nl>
cc: Nic Ferrier <nferrier@tapsellferrier.co.uk>, www-talk@w3.org, gerald@w3.org
Message-ID: <Pine.GSO.4.21.0010252113090.3058-100000@tarantula.inria.fr>
On Wed, 25 Oct 2000, Reinier Post wrote:

> About right for the client, perhaps - but for the server, which may
> have to deal with thousands of other clients at the same time?
> If requests are expensive, a few clients with persistent connections
> may occupy much of the server's capacity.

It really depends on the way the server handle persistent connection. For
server that has the knowledge of the whole server state, it is possible to
implement a LRU list of idle clients and free some when required (like in
Jigsaw [1]). Of course if your configuration is not "big" enough, this LRU
list will be too small and the timeout too short to really take benefit of
persistent connections.
I tested the timeout on a persistent connection on jigsaw.w3.org when the
load of the server is the highest and I got more than 20mn of idling
before the connection was needed by the server.

[1] http://www.w3.org/Jigsaw/

-- 
Yves Lafon - W3C / Jigsaw - XML Protocol - HTTP
"Baroula que barouleras, au tiéu toujou t'entourneras."
Received on Wednesday, 25 October 2000 15:22:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 October 2010 18:14:24 GMT