W3C home > Mailing lists > Public > www-lib@w3.org > January to March 1999

Re: Multiply requests share one socket

From: Henrik Frystyk Nielsen <frystyk@w3.org>
Date: Fri, 15 Jan 1999 16:36:54 -0500
Message-Id: <3.0.5.32.19990115163654.00bd1d30@localhost>
To: Mikhail Grouchinski <mgrouch@usa.net>, www-lib@w3.org
At 15:11 1/15/99 EST, Mikhail Grouchinski wrote:
>
>I found that libwww opens only one connection to www server.

This is a feature!

Believe me - you can run a lot faster on a single TCP connection than on
lots of small  ones, see our paper at

	http://www.w3.org/Protocols/HTTP/Performance/Pipeline.html

linked from

	http://www.w3.org/Protocols/HTTP/Performance/

>I set HTNet_maxSocket to 100 then I create 100 requests to the same host 
>and check the response time.
>
>The response time increases proportionally to the request's number. 
>Using WWWTRACE flag I can see that all other requests except one 
>are always pending and one is always in pipe 

However, it requires that you are running an HTTP/1.1 server on the other
end that is good at handling pipelining - Apache, for example, is very
good. Then you will be able to see performance figures like these:

	http://www.w3.org/Protocols/HTTP/Performance/LAN/

If you are not running against an HTTP/1.1 server then you are only gonna
get one request at a time. 

Henrik
--
Henrik Frystyk Nielsen,
World Wide Web Consortium
http://www.w3.org/People/Frystyk
Received on Friday, 15 January 1999 16:36:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 23 April 2007 18:18:28 GMT