Thanks for the quick turn around.
The reason i had the doubt was since there are 7 other webservers in the
webserver farm to which the load balancer sends requests and only the first
one seems to have 400 slots shown. The others have of the order of < 200
slots shown - though the number of active workers on each webserver is
almost the same.
Thanks
Ramdas
"Joshua Slive"
<[EMAIL PROTECTED]>
Sent by: To
[EMAIL PROTECTED] [email protected]
No Phone Info cc
Available
Subject
Re: [EMAIL PROTECTED] How to interpret
08/01/2007 06:52 server-status from mod_status
PM module?
Please respond to
[EMAIL PROTECTED]
e.org
On 8/1/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>
> I am using Apache 2.0.48 in prefork MPM mode and am not sure how to
> interpret the stat which shows "accesses this connection/child/slot".
> What is a "slot" ? The server-status shows 400 slots with most of them
> being "open slot with no process" and the rest which is less than 30
> workers being active. Does it mean at some point in time there were
400
> active workers and hence these slots were created?
Nah. You have 400 slots because MaxClients is set to 400 so apache
creates a scoreboard (inter-process communication location) with space
for 400 children to be tracked.
> Since the number of accesses/slot against the busy workers is of the
order
> of 40-50k, was wondering if forcing a value of say 10k on
> MaxRequestsPerChild would help with performace?
No, not unless you have a memory leak someplace.
Joshua.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [EMAIL PROTECTED]
" from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [EMAIL PROTECTED]
" from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
