Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:65334
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.210.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <d0d4398d8ad51ffa330d9d960bcd91a5@mail.gmail.com>
References: <d0d4398d8ad51ffa330d9d960bcd91a5@mail.gmail.com>
Date: Tue, 29 Jan 2013 13:25:54 +0400
Message-ID: <CAOc_q_xV-Se6NKgYZQ3qw+tU_F=sESd=824PHLnm5o2KcEwihA@mail.gmail.com>
To: Zeev Suraski <zeev@zend.com>
Cc: PHP Internals List <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: indeyets@gmail.com (Alexey Zakhlestin)

On Tue, Jan 29, 2013 at 1:03 PM, Zeev Suraski <zeev@zend.com> wrote:

> 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?

I use it for long-running processes, when I need something like
http://pecl.php.net/package/pthreads
But, those are scenarios, when I don't need bytecode cache, because
everything is preloaded in "real" memory

--
Alexey Zakhlestin,
http://github.com/indeyets