[Info-vax] Apache + mod_php performance
Arne Vajhøj
arne at vajhoej.dk
Sun Sep 29 10:46:12 EDT 2024
On 9/28/2024 9:41 PM, Lawrence D'Oliveiro wrote:
> On Sat, 28 Sep 2024 21:31:22 -0400, Arne Vajhøj wrote:
>> On 9/28/2024 9:18 PM, Lawrence D'Oliveiro wrote:
>>> Also, why shouldn’t a worker handle a request for another client?
>>
>> This is singlethreaded all sync workers so when they wait for a new
>> request from an existing client, then they can't handle a new client.
>
> Why not? The whole point of fork(2) is that all the processes are
> effectively clones. If you put all the client context into shared memory
> sections, then it becomes possible for any process to service any client.
>
> Of course, I’m assuming that all the processes can share the same network
> socket connections. This might not be true under VMS ...
That is not how Apache prefork MPM works.
It is not how the newer worker and event MPM's work either.
The end state sounds more like how single process multi-thread
works.
And I don't understand the "put all the client context into
shared memory" either. Are you saying that if socket descriptors
are put in shared memory then any process that map that memory
can use those sockets????
Arne
More information about the Info-vax
mailing list