-- Rafiq Ismail <[EMAIL PROTECTED]>
> There are some really graphic intensive pages here, however I'm not sure
> if Keep alive is good when there's lots of contention for pages. Should
> I:
>i) disable keep alive?
>
> ii) reduce the keep alive time out ?
>
>iii) up my nu
Rafiq Ismail <[EMAIL PROTECTED]> writes:
>iv) Something else?
Two tier Apache.
Increase shareability.
Read the guide.
--
David Hodgkinson, Wizard for Hirehttp://www.davehodgkinson.com
Editor-in-chief, The Highway Star http://www.deep-purple.com
All the Purple Family T
I agree with the response that you need to do some statistics
gathering to try to accurately isolate the cause of your problems.
I *don't* agree with the other suggestion that was made to UP the
keepalive to 15-20 seconds (the default that apache comes with is 5,
IIRC).
Here's why: Assuming tha
> Got a server which is getting hit really bad.
> Have to keep it up.
You didn't really give us enough information to guess at what your problem
is. You describe one symptom in this message: slow ping times. What else
is wrong? Are pages loading slowly? Failing to load? What applications
are
>I know this is a bit off topic, but I could use some immediate advise on
>server config?
>
>
>Got a server which is getting hit really bad.
>Have to keep it up. I've got:
>
>
>P Timeout 300
>
># Keepalive, better on this server...
>KeepAlive On
>MaxKeepAliveRequests100
>KeepAli
Your problem may be a network problem, not Apache/Mod_perl.
Check with your upstream provider and have them do a bandwidth
analysis. Here is why.
I've strobed your network and the return time latency seems to be high.
It would appear that you have about a 28 ms latency overhead in/out of
yo
I know this is a bit off topic, but I could use some immediate advise on
server config?
Got a server which is getting hit really bad.
Have to keep it up. I've got:
P Timeout 300
# Keepalive, better on this server...
KeepAlive On
MaxKeepAliveRequests100
KeepAliveTimeout
