Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:65332 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 75238 invoked from network); 29 Jan 2013 09:03:55 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Jan 2013 09:03:55 -0000 Authentication-Results: pb1.pair.com header.from=zeev@zend.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=unknown; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain zend.com does not designate 209.85.219.45 as permitted sender) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 209.85.219.45 mail-oa0-f45.google.com Received: from [209.85.219.45] ([209.85.219.45:38666] helo=mail-oa0-f45.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C8/50-07604-A7097015 for ; Tue, 29 Jan 2013 04:03:54 -0500 Received: by mail-oa0-f45.google.com with SMTP id o6so184269oag.32 for ; Tue, 29 Jan 2013 01:03:52 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:from:mime-version:x-mailer:thread-index:date:message-id :subject:to:content-type:x-gm-message-state; bh=Tuyp4tD33I29EJR8eCKlUsnB5zD+gcEViTMfazHJxI4=; b=Nox5sll7Qv1umdYVcnensGL8qXMDTM/sZUJSQF+0+wJMkWIGT/M7bWmHl7DNnJ/CGY GxUP1TCTMdsdJKMnKaBCVe/mJZcZSbOfaebNEPA0OG68hhFAVmdBDhQYOgqD3LEOlOm0 1NbP2UfmXg6y3y1yoXgCGoB2wzmXYXU63qfD9b8yfw/xm7ILaL0j4kVrYg7P+syMPIA1 r4JWVdyLk7XnuoW1Ohed7wzv63yKudtPZOGRJ52mdvEjC/wnADCDQBO4bJjiOT9g/qKr eLdp1mXbyCoExpvol+T80G8+4AgmrbXNLV+K1pNmJbeJlpVKN6ePWu+az/drYQ5L5j9n M5/A== X-Received: by 10.60.2.135 with SMTP id 7mr134114oeu.127.1359450231968; Tue, 29 Jan 2013 01:03:51 -0800 (PST) MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac39/qRu3zwbdNQUT6uiub2uYbAEbA== Date: Tue, 29 Jan 2013 11:03:51 +0200 Message-ID: To: internals@lists.php.net Content-Type: multipart/alternative; boundary=e89a8f2351fd2a93a604d469ac32 X-Gm-Message-State: ALoCoQlNjkiRbdQURvXCjwLU+VXA6ZPWch1I9yoxhcl7fH3CmPzC4nrpH0oALDq7su/a6nSq4kE1Vvc97EP0D3etMRiwU8T5FrOMbpJbR6kna0JRMtlO7+KOTQsBPsk8LzId7re+pYCq Subject: ZTS - why are you using it? From: zeev@zend.com (Zeev Suraski) --e89a8f2351fd2a93a604d469ac32 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I didn=E2=80=99t want to hijack the Optimizer+ thread so I=E2=80=99m creati= ng a new one, based on the apparent level of interest in ZTS. This isn=E2=80=99t an RFC = to remove ZTS by any stretch, but I **am** a bit confused about why people are 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 ele= gant solution exists in the form of FastCGI. Which brings me to the subject of this mail =E2=80=93 why are you using ZTS= 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 P= HP, 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? Zeev --e89a8f2351fd2a93a604d469ac32--