[In order for any reply to be added to the PR database, you need] [to include <[EMAIL PROTECTED]> in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database 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: Apache child process eats up all CPU. Comment-Added-By: stoddard Comment-Added-When: Tue May 25 07:50:49 PDT 1999 Comment-Added: What is MaxRequestsPerChild set to? I suggest you set it to 0. How much data does each CGI serve up, in the typical case? in the extreme case? How many concurrent clients are active at once? If you find you are have about as many concurrent clients as your ThreadsPerChild setting, you should 1. increase ThreadsPerChild and 2. decrease KeepAliveTimeout or disable it entirely and see if that helps. Any information that you can provide me that will help me recreate the problem would be good.
