From owner-freebsd-performance@FreeBSD.ORG Sat Feb 3 19:25:28 2007 Return-Path: X-Original-To: freebsd-performance@freebsd.org Delivered-To: freebsd-performance@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1B1A316A407 for ; Sat, 3 Feb 2007 19:25:28 +0000 (UTC) (envelope-from tom.hurst@clara.net) Received: from spork.qfe3.net (spork.qfe3.net [212.13.207.101]) by mx1.freebsd.org (Postfix) with ESMTP id D2FBA13C48E for ; Sat, 3 Feb 2007 19:25:27 +0000 (UTC) (envelope-from tom.hurst@clara.net) Received: from [81.104.144.87] (helo=voi.aagh.net) by spork.qfe3.net with esmtp (Exim 4.62 (FreeBSD)) (envelope-from ) id 1HDQBO-0006U7-HI; Sat, 03 Feb 2007 19:04:18 +0000 Received: from freaky by voi.aagh.net with local (Exim 4.66 (FreeBSD)) (envelope-from ) id 1HDQBG-000GZs-BM; Sat, 03 Feb 2007 19:04:10 +0000 Date: Sat, 3 Feb 2007 19:04:10 +0000 From: Thomas Hurst To: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <20070203190410.GA56203@voi.aagh.net> Mail-Followup-To: Miroslav Lachman <000.fbsd@quip.cz>, freebsd-performance@freebsd.org References: <45C47D49.4040101@quip.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45C47D49.4040101@quip.cz> Organization: Not much. User-Agent: Mutt/1.5.13 (2006-08-11) Sender: Thomas Hurst Cc: freebsd-performance@freebsd.org Subject: Re: PHP Performance problem after upgrade to 5.1.6 or 5.2.0 X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Feb 2007 19:25:28 -0000 * Miroslav Lachman (000.fbsd@quip.cz) wrote: > I have performance problem with PHP after upgrading from PHP 5.1.4 to > newer version regardles if newer version is 5.1.6 or 5.2.0. I tested > both with same result. Every time I upgrade PHP and see a performace regregression like this, it's been a result of forgetting to update eAccelerator, or whatever flavour of the year PHP bytecode cache is at the time. If you're sure your cache is loading (i.e. it shows up in phpinfo() and isn't logging errors on startup), you might find it useful to grab backtraces from busy processes (the source tarball includes a .gdbinit that allows you to grab PHP backtraces too, provided you're compiling with debug symbols enabled) to see where they might be spending their time. -- Thomas 'Freaky' Hurst http://hur.st/