[Info-vax] Apache + mod_php performance

Arne Vajhøj arne at vajhoej.dk
Sun Sep 29 21:41:25 EDT 2024


On 9/29/2024 9:21 PM, Lawrence D'Oliveiro wrote:
> On Sun, 29 Sep 2024 20:02:59 -0400, Arne Vajhøj wrote:
>> On 9/29/2024 7:43 PM, Lawrence D'Oliveiro wrote:
>>> On Sun, 29 Sep 2024 19:16:48 -0400, Arne Vajhøj wrote:
>>>> On 9/29/2024 6:57 PM, Lawrence D'Oliveiro wrote:
>>>>> On Sun, 29 Sep 2024 10:46:12 -0400, Arne Vajhøj wrote:
>>>>>> That is not how Apache prefork MPM works.
>>>>>
>>>>> If that’s not how it works, then how can you serve a client from more
>>>>> than one member of the worker pool?
>>>>
>>>> A new request on a new connection goes to another worker. No problem.
>>>
>>> But with keepalive, the request will come in on the existing
>>> connection. So you have to dedicate a worker process to each
>>> connection? That’s inefficient.
>>
>> There is a reason that prefork MPM has been replaced by other MPM's.
> 
> No need. Threading inherently opens its own can of worms, which is why it
> is useful to keep the option of running multiple single-threaded
> processes.

It is still an option on Linux.

But default is event.

Arne



More information about the Info-vax mailing list