httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 23117] New: - Multiple issues with Apache 2.0
Date Thu, 11 Sep 2003 20:53:09 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23117>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23117

Multiple issues with Apache 2.0

           Summary: Multiple issues with Apache 2.0
           Product: Apache httpd-2.0
           Version: 2.0.47
          Platform: PC
               URL: http://java.barchart.com
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: Other
         Component: All
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: eero@barchart.com


As a developer, I understand that this may not be a lot to go on, and possibly 
a bit vague, but I have noticed the following issues running mod_perl 1.99 and 
Apache 2.0.47 (I also tried 2.0.45 and 2.0.44)

As a note, this is running on Win2K, on a dual 733 with 512MB ram. This server 
is highly *stressed* == approximately 40 requests/sec, transferring small 
chunks of data, totaling approx. 75 kb/sec.

The perl script it simple. Launch an external program to do stuff, then return 
the STDOUT.

Problems:
1.) When Apache is run from the command line, each request spawns a new 
console. When it runs as a service, it doesn't. Problems with CreateProcess 
somewhere?

2.) The server doesn't close requests fast enough, and the requests take 
forever as the number of requests being processed grows. While I understand 
that this may just be load, it should be able to handle something like /server-
status. If not, the cpu usage should be 100%. But the cpu sits at 15 - 40 %, 
yet snags.

3.) The Apache process keeps sucking up memory. After approximately 15 minutes, 
it goes well over 100MB

4.) This is probably mod_perl: if I have let's say 100 requests, and each 
request launches abc.exe, then why am I seeing only 1, 2, sometimes 3 (but 
never 50) abc.exe's in the process list?? Does mod_perl or Apache create a 
mutex or criticalsection on this type of behavior?

Previously, I was running the same system under Apache 1.3.22 as a cgi, and it 
performed as expected. I went to mod_perl in order to kill the multiple 
perl.exe's, but the overall result is troubling.

I would be more than happy to share config files, additional info. 

EAP.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message