[Info-vax] Apache + mod_php performance

[Arne Vajhøj]

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

OK. Then it sounds like the client doesn't actually close the socket
but just stop using it and move on to a new connection.

I wonder why the HttpClient library does not do an actual close. But
it may be the best simulation of a browser - the browser doesn't know
if the user will want to view another page at the same site, so it
probably don't close the socket.

I also wonder why "Connection: close" header exist in request if the
client could just close the socket. But doesn't change how things
are.

Arne