[Info-vax] Apache + mod_php performance

[Lawrence D'Oliveiro]

On Sat, 28 Sep 2024 21:31:22 -0400, Arne Vajhøj wrote:

> On 9/28/2024 9:18 PM, Lawrence D'Oliveiro wrote:
>>
>> On Sat, 28 Sep 2024 20:50:21 -0400, Arne Vajhøj wrote:
>>
>>> The cause is that worker processes are unavailable while waiting for
>>> next request from client even though client is long gone.
>> 
>> That shouldn’t matter, if the client closed the connection properly.
> 
> It doesn't know the client closed connection.

That would only happen if the client crashed.

Note also that TLS connections require an explicit connection-closing 
exchange at the end, to guard against data-truncation attacks.

>> 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 ...