From owner-freebsd-hackers@FreeBSD.ORG Wed Mar 26 08:24:31 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 006C237B404 for ; Wed, 26 Mar 2003 08:24:31 -0800 (PST) Received: from office.advantagecom.net (office.advantagecom.net [207.109.186.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id D50E143FB1 for ; Wed, 26 Mar 2003 08:24:29 -0800 (PST) (envelope-from andykinney@advantagecom.net) Received: from SCSI-MONSTER (andy.advantagecom.net [207.109.186.200] (may be forged)) by office.advantagecom.net (8.9.3/8.9.3) with ESMTP id IAA02979; Wed, 26 Mar 2003 08:24:26 -0800 From: "Andrew Kinney" Organization: Advantagecom Networks, Inc. To: Igor Sysoev Date: Wed, 26 Mar 2003 08:24:37 -0800 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Message-ID: <3E8163C5.3024.3C0A1A9@localhost> Priority: normal References: <3E8097D4.22759.A3FC35@localhost> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12c) X-Spam-Status: No, hits=-24.6 required=5.0 tests=AWL,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, REFERENCES,REPLY_WITH_QUOTES autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) cc: freebsd-hackers@FreeBSD.ORG Subject: Re: shared mem and panics when out of PV Entries X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: andykinney@advantagecom.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Mar 2003 16:24:32 -0000 On 26 Mar 2003, at 13:29, Igor Sysoev wrote: > If you have 200M shared memory it takes about 50,000 PV entries per > process. 20 processes takes 1 million PV entries. We've got about 11.1 million PV entries to play with, so I went ahead and made MaxClients 150 just to ensure Apache couldn't panic the system at will. That combined with minimizing the KeepAliveTimeout has solved the problem for now, though I'm still not happy about letting all that RAM sit idle. I guess I'll just have to live with it. Eventually, I may be forced to turn off KeepAlive and make use of FreeBSD's accept filters or put in a reverse proxy as you recommend. For now, though, we are serving the whole gammut from this Apache. Static pages, images, mod_perl, PHP, Apache::ASP, and most anything else a customer might want or need to serve from a web server. I know it isn't the most efficient way to use Apache, but nobody has any complaints about performance at this point. Sincerely, Andrew Kinney President and Chief Technology Officer Advantagecom Networks, Inc. http://www.advantagecom.net