Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:51026 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 88443 invoked from network); 14 Dec 2010 18:27:22 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Dec 2010 18:27:22 -0000 Authentication-Results: pb1.pair.com header.from=james.butler@edigitalresearch.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=james.butler@edigitalresearch.com; spf=unknown; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain edigitalresearch.com does not designate 217.154.180.62 as permitted sender) X-PHP-List-Original-Sender: james.butler@edigitalresearch.com X-Host-Fingerprint: 217.154.180.62 analysis.edigitalresearch.com Linux 2.6 Received: from [217.154.180.62] ([217.154.180.62:53711] helo=mail.edigitalresearch.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CE/15-59442-807B70D4 for ; Tue, 14 Dec 2010 13:27:20 -0500 Received: from localhost (localhost [127.0.0.1]) by mail.edigitalresearch.com (Postfix) with ESMTP id B257F1E0031; Tue, 14 Dec 2010 18:27:15 +0000 (GMT) X-Virus-Scanned: amavisd-new at edigitalresearch.com Received: from mail.edigitalresearch.com ([127.0.0.1]) by localhost (mail.edigitalresearch.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yBXeraIxp1ES; Tue, 14 Dec 2010 18:27:14 +0000 (GMT) Received: from zarafa.localdomain (unknown [10.0.0.20]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.edigitalresearch.com (Postfix) with ESMTPS id D514E1E0007; Tue, 14 Dec 2010 18:27:14 +0000 (GMT) Received: from zarafa.edigitalresearch.com (zarafa.edigitalresearch.com [10.0.0.20]) by zarafa.localdomain (Postfix) with SMTP id 19A0E100B2F; Tue, 14 Dec 2010 18:27:14 +0000 (GMT) To: =?windows-1252?Q?Israel_Ekpo?= , =?windows-1252?Q?PHP_Internals?= Date: Tue, 14 Dec 2010 18:27:14 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable In-Reply-To: References: X-Priority: 3 (Normal) X-Mailer: Zarafa 6.40.2-22452 Thread-Index: AcubvIeIsEHiffD2Txm5aFGIszTyNA== Message-ID: Subject: RE: [PHP-DEV] PHP Performance in Apache: Multi-Process vs Multi-Threaded From: james.butler@edigitalresearch.com (=?windows-1252?Q?James_Butler?=) This is just personal experience and observation but... We are running Apache Worker with PHP safely by using PHP-FPM rather than via a shared object, so we don't have to worry about thread safety in the PHP component but can have apache multithreaded. I realise this isn't actually multi-threaded PHP but multi-process instead but s means we don't have to worry about making sure extensions etc are thread safe.=20 I haven't got the benchmarks to hand but I might able to dig some of them out if you would like. Apache Worker + FPM was definitely faster when using some simple PHP scripts to test against. Oddly we haven't noticed such a speed increase when benchmarking a Zend Framework based app, but that might be down to application oddities rather than anything else (more work/investigation needed here!).=20 Hope this is helpful. James