From owner-freebsd-performance@FreeBSD.ORG Tue May 6 04:39:17 2003 Return-Path: Delivered-To: freebsd-performance@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3AB8037B404 for ; Tue, 6 May 2003 04:39:17 -0700 (PDT) Received: from angelica.unixdaemons.com (angelica.unixdaemons.com [209.148.64.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1666043F75 for ; Tue, 6 May 2003 04:39:16 -0700 (PDT) (envelope-from hiten@angelica.unixdaemons.com) Received: from angelica.unixdaemons.com (hiten@localhost.unixdaemons.com [127.0.0.1])h46BdDww032261; Tue, 6 May 2003 07:39:13 -0400 (EDT) Received: (from hiten@localhost) by angelica.unixdaemons.com (8.12.9/8.12.1/Submit) id h46BdCAt032260; Tue, 6 May 2003 07:39:12 -0400 (EDT) (envelope-from hiten) Date: Tue, 6 May 2003 07:39:12 -0400 From: Hiten Pandya To: Sean Chittenden Message-ID: <20030506113912.GA31085@unixdaemons.com> References: <3EAE2AB9.4030408@webmatic.de> <20030505183741.GH94932@perrin.int.nxad.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030505183741.GH94932@perrin.int.nxad.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD i386 X-Public-Key: http://www.pittgoth.com/~hiten/pubkey.asc X-URL: http://www.unixdaemons.com/~hiten X-PGP: http://pgp.mit.edu:11371/pks/lookup?search=Hiten+Pandya&op=index cc: freebsd-performance@freebsd.org cc: "Thomas Krause \(Webmatic\)" Subject: Re: apache2 tuning X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 May 2003 11:39:17 -0000 Sean Chittenden (Mon, May 05, 2003 at 11:37:41AM -0700) wrote: > > I want to build a new webserver (dual xeon with 4 GB RAM). The > > server provides mostly dynamic php-pages. In the ports Makefile > > there are compile option like WITH_THREADS and WITH_MPM (which > > includes WITH_THREADS). These are useful options for a production > > machine? Also, is it useful to compile the kernel with > > ACCEPT_FILTER_DATA and ACCEPT_FILTER_HTTP? And if yes, is apache > > compiled with accept filter by default? > > Having the accept filters turned on in the kernel is a huge win for > Apache. See the tuning(7) man page for other details of interest. As > for which MPM, last I heard UNIX folk were better off using the > pre-fork MPM and not the threaded MPM. This may have changed, but I'd > bet dime to dollar you'll get better stability out of the pre-fork but > a smaller memory footprint out of the threaded MPM. -sc Turning on the Accept Filters is not the only thing you need to do. You will have to explicitly choose the type of accept filter for Apache. Last time I checked, it uses 'dataready', i.e. ACCEPT_FILTER_DATA by default. ACCEPT_FILTER_HTTP does a really good job with Apache and thttpd for that matter. Cheers! -- Hiten