Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:65363 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 27283 invoked from network); 29 Jan 2013 12:00:28 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Jan 2013 12:00:28 -0000 Authentication-Results: pb1.pair.com smtp.mail=johannes@schlueters.de; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=johannes@schlueters.de; sender-id=unknown Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error) X-PHP-List-Original-Sender: johannes@schlueters.de X-Host-Fingerprint: 217.114.211.66 config.schlueters.de Received: from [217.114.211.66] ([217.114.211.66:45315] helo=config.schlueters.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E0/93-10721-BD9B7015 for ; Tue, 29 Jan 2013 07:00:28 -0500 Received: from [192.168.2.20] (ppp-93-104-29-211.dynamic.mnet-online.de [93.104.29.211]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by config.schlueters.de (Postfix) with ESMTPSA id 6EC71653DE; Tue, 29 Jan 2013 13:00:23 +0100 (CET) To: Pierre Joye Cc: Zeev Suraski , PHP internals In-Reply-To: References: <1359459921.3916.105.camel@guybrush> Content-Type: text/plain; charset="UTF-8" Date: Tue, 29 Jan 2013 13:01:20 +0100 Message-ID: <1359460880.3916.136.camel@guybrush> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] ZTS - why are you using it? From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Tue, 2013-01-29 at 12:49 +0100, Pierre Joye wrote: > > That is true. Many modern compilers and environments provide better > > support for thread local storages .... > > Exactly, or more exactly CRTs (libc, crt and the likes)> That's what I called "environment" - some of these things depend on kernels, some on libraries, ... anyway - irrelevant terminology :-p > > What I see is that TSRM brings a lot of complexity and introduces risk > > of bugs in there as many developers don't think about. Most of us are > > focused on the nice and simple world of single-threaded computing. And I > > assume that we can still find quite some threading bugs when going on a > > hunt for them ... so besides of pure executable performance there is > > also the cost of developer power for (proper) maintenance ... > > The amount of bugs is rather low. We do test in TS and TS on a daily > basis. The last extension causing more critical issues was mysql, we > have discussed these bugs for a long time. There were mysqli threading bugs, the last one of those actually had been engine bugs which affected other extensions, too. See i.e. http://news.php.net/php.internals/59353 Such bugs identified a year after the release of 5.4 gives me quite a good indication of the little actual testing being done overall. johannes