Re: os-windows/3815: Keep Alive option let server response delay at first request.

[Lee ChihCheng <le...@catlover.com>]

The following reply was made to PR os-windows/3815; it has been noted by GNATS.

From: Lee ChihCheng <le...@catlover.com>
To: stoddard@apache.org, apbugs@Apache.Org
Cc:  Subject: Re: os-windows/3815: Keep Alive option let server response delay at 
 first request.
Date: Thu, 29 Apr 1999 20:41:05 +0800

 Dear sir:
 
   Sorry, My earlier post is not really right.
 
   After few days watch, I found the reason is because my site is too busy.   
 
   Now my Apache setting is like:
   -------------------------
   KeepAlive Off
   MaxKeepAliveRequests 0
   KeepAliveTimeout 20
   MaxRequestsPerChild 0
   ThreadsPerChild 256
   -------------------------
 
   And I use http://mysitename/server-staus to check it, screen show:
 
   130 requests currently being processed, 126 idle servers
 
   So, When I switch to "KeepAlive On", the "MaxKeepAliveRequests" is not enough.
   (I think maybe 300~800 users online, if keep-alive)
    
   I don't understand why Apache server never tell me "too busy", Apache just 
   delay each web-page "first" 3~4 seconds.  (sometimes 10~15 seconds)
 
   So, I disable KeepAlive now.
 
   However I hope user can keep-alive, But I found Apache's Windows version just support
   max 256 users keep-alive.  it's too small for me.
 
   And I found the only way to expand this number is "modify the source, re-compiler it"
   but it's too hard for me...
 
   I hope the future version's apache can expand this limit.
 
   There is also a small problem.
 
   "Apache -k restart"  can restart apache.  but not immediately.
   If I send this command at PM23:30, the Apache will restart at AM1:00 ~ AM2:00
   It's really too late.
 
   Thanks for your reply , and sorry for my broken english.
 
 Lee-1
 
 
 
   
 
 
 
 stoddard@apache.org wrote:
 > 
 > [In order for any reply to be added to the PR database, ]
 > [you need to include <ap...@Apache.Org> in the Cc line ]
 > [and leave the subject line UNCHANGED.  This is not done]
 > [automatically because of the potential for mail loops. ]
 > [If you do not include this Cc, your reply may be ig-   ]
 > [nored unless you are responding to an explicit request ]
 > [from a developer.                                      ]
 > [Reply only with text; DO NOT SEND ATTACHMENTS!         ]
 > 
 > Synopsis: Keep Alive option let server response delay at first request.
 > 
 > State-Changed-From-To: open-feedback
 > State-Changed-By: stoddard
 > State-Changed-When: Wed Apr 28 21:10:59 PDT 1999
 > State-Changed-Why:
 > How are you starting the server after the change? (What command are you using?).
 > If you start Apache from the command line using 'apache', the server will not come up for
 > several seconds (it is querying the service manager, which is unnecessary if apache is
 > run from the command line). If you try with 'apache -s', you will not see this
 > delay in starting. Could this be the problem you are seeing?
 > it comes up immediately. -s tells the
 > server not to try to query the service manager