| 1 |
>> Assuming you have the concept right, if I have 'MaxClients 50' and |
| 2 |
>> 'MaxSpareServers 10', there should never be more than 60 apache2 |
| 3 |
>> processes running and I should be able to serve up to 50 simultaneous |
| 4 |
>> TCP sessions? |
| 5 |
> |
| 6 |
> I'd guess it wouldnt go past 50. |
| 7 |
> |
| 8 |
>> Can anyone explain why I have 20 apache2 processes running moments |
| 9 |
>> after an apache2 restart with 'MaxSpareServers 10' and without more |
| 10 |
>> than 1 or 2 simultaneous TCP sessions? |
| 11 |
> |
| 12 |
> Do you have StartServer set to 10 (default is 2 or 3) |
| 13 |
> Have any TCP sessions recently closed? Maybe the Server isn't |
| 14 |
> re-cycled until the *_WAIT TCP states have timed out. |
| 15 |
|
| 16 |
Do you know if MaxClients includes clients associated with *_WAIT TCP |
| 17 |
states? I'm trying to figure out the hard limit on apache2 processes |
| 18 |
according to my config so I can plan for memory usage accordingly, but |
| 19 |
I get the feeling I'm going about it the wrong way. Doesn't every |
| 20 |
sysadmin need to do this to make sure they don't run out of memory? |
| 21 |
|
| 22 |
I have: |
| 23 |
|
| 24 |
StartServers 5 |
| 25 |
MinSpareServers 5 |
| 26 |
MaxSpareServers 10 |
| 27 |
MaxClients 50 |
| 28 |
MaxRequestsPerChild 10000 |
| 29 |
|
| 30 |
- Grant |
Archives