From owner-freebsd-current@FreeBSD.ORG Tue Apr 22 20:34:30 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 80DD3106566B for ; Tue, 22 Apr 2008 20:34:30 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id EE9738FC26 for ; Tue, 22 Apr 2008 20:34:29 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JoPC7-0005cN-Ai for freebsd-current@freebsd.org; Tue, 22 Apr 2008 20:34:27 +0000 Received: from 89-172-63-116.adsl.net.t-com.hr ([89.172.63.116]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 22 Apr 2008 20:34:27 +0000 Received: from ivoras by 89-172-63-116.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 22 Apr 2008 20:34:27 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Tue, 22 Apr 2008 22:34:14 +0200 Lines: 58 Message-ID: References: <8481.1208889581@critter.freebsd.dk> <480E3E66.3000303@samsco.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigBDB43C503C6CB24D67C942EF" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 89-172-63-116.adsl.net.t-com.hr User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) In-Reply-To: <480E3E66.3000303@samsco.org> X-Enigmail-Version: 0.95.6 Sender: news Subject: Re: Http Accept filters (accf_http) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Apr 2008 20:34:30 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigBDB43C503C6CB24D67C942EF Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Scott Long wrote: > Poul-Henning Kamp wrote: >> In message <480E307B.901@quis.cx>, Jille writes: >>> Hello, >>> >>> I've read about accf_http(9) some time ago, and I was wondering about= =20 >>> it's performance. >>> Does it increase performance on all workloads ? >>> (I'm intrested in the improvements for a PHP-apache-webserver with=20 >>> about 50 request/second average.) >> >> I doubt you will see measurable performance difference from using >> request filters at such low traffic. >> >=20 > The accept filters do reduce service latency and probably have a small > benefit in CPU utilization. 50 requests/sec is probably enough to see > a benefit for something like PHP or PERL. It definitely won't hurt, an= d > even if there's no measurable benefit now, it'll help prepare you for > scaling in the future. Does anyone know why accf_accept is disabled by default in the ports'=20 stock Apache 2.2 (it's disabled in the default config files)? I thought=20 it was because it was dangerous or flawed for some reason, though (at=20 least for light loads comparable to those of OP) it seems to work fine. As to the original question: theoretically it could help requests for=20 images and similar small objects - PHP scripts execute too long for the=20 benefits to be visible. In my own case, though, I couldn't discern a=20 difference with and without accf_httpd. One other thing is that=20 keepalives essentially nullify the effects of the filter (as far as I=20 understand, the filter only works on the first bytes after the=20 connection is established), but keepalives can help performance much=20 more than accfs. --------------enigBDB43C503C6CB24D67C942EF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIDkvGldnAQVacBcgRAvlvAJ9IiuTGHia4PJYCV8fN3TtV3TzFyQCg62Ci fardCjh1eSq4h6nXXILCxX0= =JBBF -----END PGP SIGNATURE----- --------------enigBDB43C503C6CB24D67C942EF--