Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101993
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain librelamp.com designates 45.79.96.192 as permitted sender)
To: internals@lists.php.net
References: <CADbOR2jGipMjHGNYHO-hqkcYo_mNovJoxnuMB+RvPqe3PdMhTg@mail.gmail.com>
 <421fae6f-d6ba-1990-d3d8-9ac236313cea@evermeet.cx>
Message-ID: <360598cf-f723-1279-0a95-3c5055447fe8@librelamp.com>
Date: Wed, 21 Mar 2018 22:52:51 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <421fae6f-d6ba-1990-d3d8-9ac236313cea@evermeet.cx>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] what's the official position on apache threaded
 environments
From: alice@librelamp.com (Alice Wonder)

On 03/21/2018 09:15 PM, Helmut K. C. Tessarek wrote:
> On 2018-03-21 21:59, j adams wrote:
>> So what's the story with PHP and multithreaded environments these days?
>
> Unfortunately PHP was never and will most likely never be threadsafe as
> a module.
> (Yes, I know that there's the ZTS code, but hey, are you really serious
> about this?)
> I never understood why the core devs never switched to a threaded model,
> but I believe they never deemed it truly necessary.
> The ZTS threaded module has a few interesting approaches but fails in
> some other areas. To be honest, I suggest to use the fpm-cgi SAPI module
> with an Apache threaded environment.

I've been using zts w/ latest apache in threaded and have not found the 
issues, but I've heard Remi mention them and he generally knows all 
things truth from fiction when it comes to php.

Is there a list somewhere of what the specific issues with using zts in 
multi-threaded apache are? What modules have known issues?

I haven't found it.