Re: Impact of the number of TCP/IP connections on the same port on Apache web server performance
From: Rick Jones (foo_at_bar.baz.invalid)
Date: 03/03/04
- Next message: nospam: "Re: CAP on Tru64 5.1B"
- Previous message: Bev A. Kupf: "Re: CAP on Tru64 5.1B"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 03 Mar 2004 00:54:37 GMT
There are some old SPECweb99 and SPECweb96 disclosures for Tru64 at
http://www.spec.org/ . They are likely all for Zeus, rather than
Apache, but perhaps some of the settings might be germane.
I cannot speak directly to Tru64, but on HP-UX, if there were only 20
hits per second, I don't think that splitting things across multiple
listen endpoints would make much of a difference. At least not so far
as networking is concerned.
BTW, as far as having 100 connections on one and the same port, that
is only the local port. The TCP connections themselves are "named"
with the four-tuple of local/remote port, local/remote IP, and about
the only place I can think of in a TCP/IP stack where the one
well-known port could be a bottleneck is during connection
establishment as that is the only time things feed just through the
listen socket.
rick jones
-- Process shall set you free from the need for rational thought. these opinions are mine, all mine; HP might not want them anyway... :) feel free to post, OR email to raj in cup.hp.com but NOT BOTH...
- Next message: nospam: "Re: CAP on Tru64 5.1B"
- Previous message: Bev A. Kupf: "Re: CAP on Tru64 5.1B"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|