Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:65335 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 81089 invoked from network); 29 Jan 2013 09:29:14 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Jan 2013 09:29:14 -0000 Authentication-Results: pb1.pair.com header.from=laruence@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=laruence@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.179 as permitted sender) X-PHP-List-Original-Sender: laruence@gmail.com X-Host-Fingerprint: 209.85.217.179 mail-lb0-f179.google.com Received: from [209.85.217.179] ([209.85.217.179:54218] helo=mail-lb0-f179.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 2C/81-07604-66697015 for ; Tue, 29 Jan 2013 04:29:11 -0500 Received: by mail-lb0-f179.google.com with SMTP id j14so447116lbo.10 for ; Tue, 29 Jan 2013 01:29:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=vB0Gz+pPb4nv3h+R87FYQqXIGVQ9tYrZLw/CEb2ZkAk=; b=jXVyu8dNxPVuOOezx6BvdnzU3BSrlVSQqIJddRH071Fpyzv7ALapcaUXtdTqRZpZDK gx7DYit6GAWNNBMp8gIIBJ0T+4wbgKAORW8lYDvGwYHJWGktuLVeZ88dll8TP6DWz6R5 zSTLXUEJROMflNEAEMnnk/mg/3CzdyFbEQBQ7tRAmWP59rz5ubuaXP/J1QarXgdru86v 8kw0odMUDdfh2rtDrMDca9vWyG4X4eVzGN5p4WBr9ldrCs0875eRSVktzB9EFsz0I9vp bY4SS2YgsW2xziXn29EaEYhYQan1viSZlKe4kwj+el3ASw1UhKjurpnxHC8UCAZ9Zd2Y 6jMA== X-Received: by 10.112.101.230 with SMTP id fj6mr173239lbb.115.1359451746548; Tue, 29 Jan 2013 01:29:06 -0800 (PST) MIME-Version: 1.0 Sender: laruence@gmail.com Received: by 10.114.66.196 with HTTP; Tue, 29 Jan 2013 01:28:46 -0800 (PST) In-Reply-To: References: Date: Tue, 29 Jan 2013 17:28:46 +0800 X-Google-Sender-Auth: pZxE-Q770NKqJe_VaZx1IU8-Yso Message-ID: To: Zeev Suraski Cc: internals@lists.php.net Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] ZTS - why are you using it? From: laruence@php.net (Laruence) On Tue, Jan 29, 2013 at 5:03 PM, Zeev Suraski wrote: > I didn=E2=80=99t want to hijack the Optimizer+ thread so I=E2=80=99m crea= ting a new one, > based on the apparent level of interest in ZTS. This isn=E2=80=99t an RF= C to > remove ZTS by any stretch, but I **am** a bit confused about why people a= re > still using ZTS. > > > > A bit of background. I started the ZTS project (based on initial work by > Shane Caraveo more than a decade ago), and invested countless hours in > pushing it all throughout PHP. So I really hold absolutely no grudge > against it, quite the contrary=E2=80=A6 However, many years ago, I came = to the > conclusion that it was a bit of a lost cause trying to weed out all the > thread safety issues from everywhere =E2=80=93 and that a simpler, more e= legant > solution exists in the form of FastCGI. > > > > Which brings me to the subject of this mail =E2=80=93 why are you using Z= TS PHP > instead of single threaded PHP? The reasons not to use it are few but > fairly major =E2=80=93 it=E2=80=99s significantly slower than the non-ZTS= PHP, and it=E2=80=99s > significantly less robust in the sense that a single bug somewhere can > bring down an entire server (or at least a bunch of many different > threads). What are your reasons to choose it over FastCGI? Hey: It's not we choose ZTS, it is there are many users run with them (IIS, Apache+workers, and pthreads extension require it) and all PHP extensions supports it, so if O+ doesn't, it feel a little inconsistent. thanks > > > > Zeev --=20 Laruence Xinchen Hui http://www.laruence.com/