[Info-vax] Apache + mod_php performance

[Simon Clubley]

On 2024-10-02, Arne Vajhøj <arne at vajhoej.dk> wrote:
> On 10/2/2024 1:52 PM, Simon Clubley wrote:
>> On 2024-10-02, Arne Vajhøj <arne at vajhoej.dk> wrote:
>>> On 10/2/2024 11:07 AM, Dan Cross wrote:
>>>> In article <vdjmq4$37f8q$3 at dont-email.me>,
>>>> Arne Vajhøj  <arne at vajhoej.dk> wrote:
>>>>> On 10/2/2024 10:47 AM, Dan Cross wrote:
>>>>>> [snip]
>>>>>> You do not seem to understand how this is qualitatively
>>>>>> different from your test program not sending `Connection: close`
>>>>>> with its single request per connection, and then blocking until
>>>>>> the server times it out.
>>>>>
>>>>> It is qualitative different from what you are imaging.
>>>>>
>>>>> The client does not block until the server times out.
>>>>
>>>> So what, exactly, does it do?
>>>
>>> It moves on to next request.
>> 
>> Does it reuse an existing connection for the next request (which is
>> what you have told the server you are going to do due to your keep-alive
>> settings) or does it always create a brand-new connection for the next
>> request ?
>
> New connection.
>
> It is simulating multiple browser instances.
>
> Browser #1 open connection to request the page - keep
> the connection alive, because it may want to use it later.
>
> Browser #2 open connection to request the page - keep
> the connection alive, because it may want to use it later.
>

Are you closing down the current instance of the client and then
starting up a new instance of the client ?

or

Are you keeping the existing process running and creating a new
instance from it ?

In either case, are you _cleanly_ and _fully_ closing the existing
connection _before_ you exit or create a new connection in the existing
process ?

Simon.

-- 
Simon Clubley, clubley at remove_me.eisner.decus.org-Earth.UFP
Walking destinations on a map are further away than they appear.