[815] in linux-net channel archive
Increasing TCP listen backlog: www server
daemon@ATHENA.MIT.EDU (Robert Stockmann)
Tue Aug 1 15:27:50 1995
From: stock@cpt7.stm.tudelft.nl (Robert Stockmann)
To: linux-net@vger.rutgers.edu
Date: Mon, 31 Jul 1995 02:38:47 +0200 (MET DST)
Hi,
I've been looking at the apache pages at ssc.com, and from there
there are some interresting pages at www.sun.com about tuning
your server for high www load. First of all they mention to
use the netscape server.. Ok thats fine, but I want to use a P90
with Linux for www services. So I'm thinking about apache.
Second they mention to put the server as a standalone instead of
running it from inetd. Makes sense...
Third they say to "Increase the TCP listen backlog". This seems to
me a usefull tip. Its mentioned to replace in the source of webserver
the call's for listen(s,5) with listen(s,32) for instance...
In solaris there is a command for increasing the backlog for the system
by using the command:
/usr/sbin/ndd -set /dev/tcp tcp_conn_req_max 32
And the results are that on suns you'll find this:
R = 5 connections / 500 ms
= 10 connections/sec (Solaris 2.4 using default backlog)
R = 32 connections / 500 ms
= 64 connections/sec (Solaris 2.4 using increased backlog)
This is not bad..But when reading the manpages (man 2 listen) I read:
BUGS
The backlog is currently limited (silently) to 5. [Docu-
menter's note: is this true for Linux?]
So whats the actual status of the listen() syscall right now for Linux??
Robert
--
++---------------------------++----------------------------------------++
|| R.M. Stockmann || Delft University of Technology ||
|| stock@cpt7.stm.tudelft.nl || Department of Chemical Engineering ||
|| phone: +31 15 784395 || Section Industrial Catalysis ||
|| home: +31 1620 36177 || Julianalaan 136 ||
|| fax: +31 17 784452 || 2628 BL Delft The Netherlands ||
++---------------------------++----------------------------------------++
