Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:21113 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 81629 invoked by uid 1010); 8 Dec 2005 11:17:40 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 81614 invoked from network); 8 Dec 2005 11:17:40 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Dec 2005 11:17:40 -0000 X-Host-Fingerprint: 194.109.253.196 mediawave.xs4all.nl Linux 2.5 (sometimes 2.4) (4) Received: from ([194.109.253.196:37545] helo=mediawave.nl) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id F9/D2-14828-35618934 for ; Thu, 08 Dec 2005 06:17:40 -0500 Received: from mediawave.nl (mediawave.nl [127.0.0.1]) by mediawave.nl (8.13.4/8.13.4) with ESMTP id jB8BHbf5021381; Thu, 8 Dec 2005 12:17:37 +0100 Received: (from apache@localhost) by mediawave.nl (8.13.4/8.13.4/Submit) id jB8BHa2a021380; Thu, 8 Dec 2005 12:17:36 +0100 X-Authentication-Warning: mediawave.nl: apache set sender to bart@mediawave.nl using -f Received: from 137.224.252.10 (SquirrelMail authenticated user bart) by www.mediawave.nl with HTTP; Thu, 8 Dec 2005 12:17:36 +0100 (CET) Message-ID: <34083.137.224.252.10.1134040656.squirrel@www.mediawave.nl> In-Reply-To: <4e89b4260512071917s2a4e0977tcc29ec895966568d@mail.gmail.com> References: <22.BF.14828.12287934@pb1.pair.com> <43978303.3070809@lerdorf.com> <92549A1E-EEAD-46EA-B956-5EA3A2F1FBC7@gravitonic.com> <4e89b4260512071917s2a4e0977tcc29ec895966568d@mail.gmail.com> Date: Thu, 8 Dec 2005 12:17:36 +0100 (CET) To: lsmith@php.net Cc: internals@lists.php.net User-Agent: SquirrelMail/1.4.6 [CVS]-0.cvs20050812.1.fc4 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Re: [PHP-DEV] Multithreading From: bart@mediawave.nl ("Bart de Boer") > I really do not see the point is worrying all too much about multi > threading in PHP. Writing proper multi threaded code is hard and why > bother? Your server is going to be busy doing tons of other things at > the same time. So all your CPU's and cores should have plenty of things > to do. Also PHP is a glue language, so by this virtue it should not > require multi threading in order to get decent performance/latency for a > History tells us that, as hardware performance increases, people will always utalise the extra power by creating more demanding scripts (and software). We most likely wouldn't do the things we do today if we still had the hardware we had back when PHP3 was out. Since it currently seems to be the trend that performance gains are made by adding more cores to the processor, I think the server software must adjust to be able to utalise this. I have a feeling we'll be seeing a lot more multithreading software in the near future. Although you're right that the webserver already does multithreading itself. And PHP is able to hitch a ride on this capability. I just think that maybe, if the multithreading trend really takes off, it may one day become a necessity for PHP to support this. If so, I don't think it will be in the near future. So there's still plenty of time to think about this. :) Of course this is all "what-if" speculation. But I thought it's worth noting at least. :) > the language. So I welcome whatever Sara is playing with that can be > added as an extension to PHP.