From owner-freebsd-performance@FreeBSD.ORG Mon May 5 11:37:43 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 3F1C837B401 for ; Mon, 5 May 2003 11:37:43 -0700 (PDT) Received: from perrin.int.nxad.com (internal.ext.nxad.com [69.1.70.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id C895543FDF for ; Mon, 5 May 2003 11:37:42 -0700 (PDT) (envelope-from sean@perrin.int.nxad.com) Received: by perrin.int.nxad.com (Postfix, from userid 1001) id 7F40D21058; Mon, 5 May 2003 11:37:41 -0700 (PDT) Date: Mon, 5 May 2003 11:37:41 -0700 From: Sean Chittenden To: "Thomas Krause (Webmatic)" Message-ID: <20030505183741.GH94932@perrin.int.nxad.com> References: <3EAE2AB9.4030408@webmatic.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3EAE2AB9.4030408@webmatic.de> User-Agent: Mutt/1.4i X-PGP-Key: finger seanc@FreeBSD.org X-PGP-Fingerprint: 3849 3760 1AFE 7B17 11A0 83A6 DD99 E31F BC84 B341 X-Web-Homepage: http://sean.chittenden.org/ cc: freebsd-performance@freebsd.org 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: Mon, 05 May 2003 18:37:43 -0000 > 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 -- Sean Chittenden