From owner-freebsd-hackers Thu Jan 28 11:20:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27724 for freebsd-hackers-outgoing; Thu, 28 Jan 1999 11:20:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27719 for ; Thu, 28 Jan 1999 11:20:38 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id LAA10349; Thu, 28 Jan 1999 11:20:36 -0800 (PST) (envelope-from dillon) Date: Thu, 28 Jan 1999 11:20:36 -0800 (PST) From: Matthew Dillon Message-Id: <199901281920.LAA10349@apollo.backplane.com> To: Matthew Dillon Cc: "John S. Dyson" , dyson@iquest.net, wes@softweyr.com, toasty@home.dragondata.com, hackers@FreeBSD.ORG Subject: Re: High Load cron patches - comments? References: <199901281845.NAA21716@y.dyson.net> <199901281902.LAA10225@apollo.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since I'm using sendmail a little too much as an example, I'll use BEST's web server as another example. The web server hard limits the number of simultanious connections. On a relatively loaded machine, say shell5.ba.best.com, the peak utilization is fairly consistent. The monday-noon peak runs at 35 hits/sec and 500 simultanious established connections. We set the hard limit to around 800 simultanious established connections. In this case, the hard limit is mainly designed to handle occassional bursts of CGIs that eat into the number of connections and to give the server enough room to handle one or two users being listed as 'best site of the day' on Yahoo or something like that, something that might happen once a month. The hard limit is also designed to handle runaway CGIs. It is set high enough that it never gets hit under normal operating conditions, but low enough that the server doesn't fall on its face if someone CGI-fork-bombs the server. The sysop can usually get in and fix the problem without having to even restart the web server, which is a big plus. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message