Re: Apache + mod_php performance

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

I don't work much with this kind of stuff, but I have questions?
If a connection is persistent, then there is already a connection, no need for a "brand-new" connection.  However, perhaps you're asking whether the client uses an existing connection, or always issues a new connection request?
In the web services I've implemented in the past, the protocol was rather simple.  Request a connection, perform transaction, close connection.
It did bite us on the ass one time.  The client would be requesting inventory status for individual parts.  The programmer on the client side (not us) was issuing requests for one part number for each connection.  That wasn't good. Once we pointed out to him/her that the protocol would accept multiple part numbers in a single transaction, could be thousands, the problem disappeared.
The thing is, either have well defined transactions, or, be a "jack-of-all-trades" and do nothing well.
--
David Froble                       Tel: 724-529-0450
Dave Froble Enterprises, Inc.      E-Mail: davef@tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA  15486