Re^2: 'A' web server takes another "time out"

[mda2]

On my experience, is very important correct values for:

• MaxClient -> 100 Ok (it's can be more)
• MinSpareServers -> min free instances, sugest same of StartServers
• MaxSpareServers -> max free instances, sugest more than 60% of MaxClients
• MaxKeepAliveRequests -> never all instances, sugest 50% of MaxClient
• MaxRequestPerChild -> max request before kill process, set if required...

Some time ago I had make a node Monitor instances of Apache Web server, with a script to see how are use of apache web connections online. To see historical usage, I'm sugest to use it or Apache-Tools (from Apache-Security).

Evaluating your load averages, swap and CPU states, on my opinion optimize apache make good results... See your running time of httpd process:

$ grep httpd 547234 | awk '{print $8}' | sort | uniq -c | head -n 5
    125 0:00
    110 0:01
     41 0:02
     14 0:03
      9 0:04

But the great info is "Parent Server Generation: XX" on server-status ... You realy need to enable this module ;)

Current Time: Friday, 05-May-2006 10:56:47 PDT
Restart Time: Tuesday, 02-May-2006 10:24:02 PDT
Parent Server Generation: 3
Server uptime: 3 days 32 minutes 45 seconds
Total accesses: 16557075 - Total Traffic: 349.2 GB
CPU Usage: u170.547 s310.375 cu0 cs0 - .184% CPU load
63.4 requests/sec - 1.4 MB/second - 22.1 kB/request
175 requests currently being processed, 81 idle workers

CKWWCKK_K_K_CKC_KK_K___KKK__K_KKKKKKKC_K_CC_KWK__WKKK_K_WKKK__WK
GGG.GG.G.GGG...GGGGG..GGG.GGG.GG..GG.G..GG..G.....GWGGGGGGGGGGGG
.G...W.GG.....G.GG.G..G.GG.........GGWG.G..G.G.....G...WG....G.G
_K__KKCKCKWCK_WK__KKK_K_KW_KC__W___KKKK_KKKCK_KKWKKC_KCKKWKCKKWC

[samtregar]

MaxClients of 100 seems pretty high to me. Commodity hardward isn't going to deal with 100 simultaneous mod_perl jobs very well! Even if you have the memory to handle that many jobs, you probably don't have the CPU.

MaxClients can be high on a front-end server which serves static content and does a reverse proxy to the mod_perl backend. Those servers do much less work per-request and a given machine can run more of them simultaneously.

-sam