Sujet : Re: Apache + mod_php performance
De : cross (at) *nospam* spitfire.i.gajendra.net (Dan Cross)
Groupes : comp.os.vmsDate : 02. Oct 2024, 16:42:54
Autres entêtes
Organisation : PANIX Public Access Internet and UNIX, NYC
Message-ID : <vdjplu$fk2$1@reader1.panix.com>
References : 1 2 3 4
User-Agent : trn 4.0-test77 (Sep 1, 2010)
In article <
vdjocl$37f8p$3@dont-email.me>,
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 the client close the connection? Why do you think that it
moves on to the next request?
Despite repeated requests for more information, you haven't told
us much of anything at all about the client or your setup. I
gather that the client is something you wrote yourself; why not
put that code somewhere for someone else to inspect and
understand?
That request will block if the server can't serve it
because all processes are busy.
You haven't shown sufficient evidence to support that
conclusion; perhaps you have it, but you haven't shared
it. Have you even attempted any of the debugging steps
I suggested to you, for instance?
And what is the "problem" that
you are imagining here? Please be specific.
>
Go back to the first post in the thread.
>
The numbers for Apache are low. Much lower than
for other servers.
Yes. I don't see any evidence to support your claims.
- Dan C.