From owner-freebsd-apache@FreeBSD.ORG Wed Feb 15 21:10:23 2006 Return-Path: X-Original-To: freebsd-apache@freebsd.org Delivered-To: freebsd-apache@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8F0116A420 for ; Wed, 15 Feb 2006 21:10:23 +0000 (GMT) (envelope-from bsdlists@celeritystorm.com) Received: from mail.celeritystorm.com (213-247-62-79.ip.netshark.nl [213.247.62.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6E1C43D69 for ; Wed, 15 Feb 2006 21:10:17 +0000 (GMT) (envelope-from bsdlists@celeritystorm.com) Received: by mail.celeritystorm.com (Postfix, from userid 106) id D5CBB3D8121; Wed, 15 Feb 2006 22:34:02 +0100 (CET) Received: from [192.168.0.1] (unknown [81.84.174.6]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.celeritystorm.com (Postfix) with ESMTP id 831EF3D80DA; Wed, 15 Feb 2006 22:34:02 +0100 (CET) Message-ID: <43F398B8.2000103@celeritystorm.com> Date: Wed, 15 Feb 2006 21:10:16 +0000 From: BSD User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040724) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Clement Laforet , freebsd-apache@freebsd.org References: <43F3539E.5080007@celeritystorm.com> <20060215210533.GB59145@goofy.cultdeadsheep.org> In-Reply-To: <20060215210533.GB59145@goofy.cultdeadsheep.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Apache 1.3 + PHP 5 on FreeBSD 6 -- bad performance under load X-BeenThere: freebsd-apache@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Support of apache-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Feb 2006 21:10:23 -0000 Clement Laforet wrote: >On Wed, Feb 15, 2006 at 04:15:26PM +0000, BSD wrote: > > >>As you can see, it took 10 seconds to reply to the GET, yet the >>accepting of the connection was instant. >>I have more than enough maxfiles, maxproc, maxfilesperproc, nmbclusters >>etc. I guess the connection is so promptly answered because of the http >>accept filters built in the kernel. >> >>As a final note, the MaxClients I'm using are not nearly enough (around >>200 connections/second, according to pfstat graphics vs MaxClients 98). >>The reason for this is that trying to match MaxClients with the real >>load resulted in two 0.0% idle processors, since the PHP code is a bit >>heavy. I've opted to disable KeepAlive and lower MaxClients instead. >>Could this be the delay I'm seeing ? I think so, but I need more >>opinions, so feel free to reply. >> >> > >It looks like requests are stuck in the listen backlog. > >clem > > That is my main suspect too. Is there a way to know how many connections are currently on the backlog ?