Path: ...!weretis.net!feeder9.news.weretis.net!panix!.POSTED.spitfire.i.gajendra.net!not-for-mail
From: cross@spitfire.i.gajendra.net (Dan Cross)
Newsgroups: comp.os.vms
Subject: Re: Apache + mod_php performance
Date: Tue, 1 Oct 2024 19:45:47 -0000 (UTC)
Organization: PANIX Public Access Internet and UNIX, NYC
Message-ID: <vdhjhb$oid$1@reader1.panix.com>
References: <vcv0bl$39mnj$1@dont-email.me> <vd7j5q$t5d$1@reader1.panix.com> <vd7l3k$tgu3$4@dont-email.me> <vd9mqn$1cm1v$1@dont-email.me>
Injection-Date: Tue, 1 Oct 2024 19:45:47 -0000 (UTC)
Injection-Info: reader1.panix.com; posting-host="spitfire.i.gajendra.net:166.84.136.80";
	logging-data="25165"; mail-complaints-to="abuse@panix.com"
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
Originator: cross@spitfire.i.gajendra.net (Dan Cross)
Bytes: 1678
Lines: 25

In article <vd9mqn$1cm1v$1@dont-email.me>,
Dave Froble  <davef@tsoft-inc.com> wrote:
>On 9/27/2024 9:11 PM, Arne Vajhøj wrote:
>[snip]
>> I believe that server config supporting keep alive
>> causing performance to drop to 1/10'th for clients
>> not using keep alive is a bug.
>>
>> Arne
>
>Feature ...

Yes, it is a feature, despite this report of a non-problem.

In this case, later posts revealed the real culprit: Arne's test
program did not follow the protocol, and was not sending
`Connection: close` with an HTTP/1.1 request; in response, the
server (correctly) kept the connection open waiting for the
client to send another request.

It is illustrative how OP immediately blamed the server, the
least likely outcome, without sufficiently investigating and
finding his own error.

	- Dan C.