Path: ...!3.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP>
Newsgroups: comp.os.vms
Subject: Re: Apache + mod_php performance
Date: Wed, 2 Oct 2024 18:15:26 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 54
Message-ID: <vdk2ju$3bapl$1@dont-email.me>
References: <vcv0bl$39mnj$1@dont-email.me> <vdjjpv$37f8q$2@dont-email.me> <vdjme2$r42$4@reader1.panix.com> <vdjmq4$37f8q$3@dont-email.me> <vdjnk0$2ob$1@reader1.panix.com> <vdjocl$37f8p$3@dont-email.me> <vdk193$3auiu$2@dont-email.me> <vdk1iv$37f8q$5@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 02 Oct 2024 20:15:26 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="52d5a78822066480580ced5a21c277bc";
	logging-data="3517237"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19DJiqtqQ7SR+iDqH4FQJEfRlk94Aq7UR0="
User-Agent: slrn/0.9.8.1 (VMS/Multinet)
Cancel-Lock: sha1:wZqlbMqYXhpJw+YkTSU3bpbV4ys=
Bytes: 3079

On 2024-10-02, Arne Vajhøj <arne@vajhoej.dk> wrote:
> On 10/2/2024 1:52 PM, Simon Clubley wrote:
>> On 2024-10-02, Arne Vajhøj <arne@vajhoej.dk> wrote:
>>> On 10/2/2024 11:07 AM, Dan Cross wrote:
>>>> In article <vdjmq4$37f8q$3@dont-email.me>,
>>>> Arne Vajhøj  <arne@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@remove_me.eisner.decus.org-Earth.UFP
Walking destinations on a map are further away than they appear.