Thanks Perrin, Here is the part of the httpd.conf that I believe you wanted to see.
# # Apache on Win32 always creates one child process to handle requests. If it # dies, another child process is created automatically. Within the child # process multiple threads handle incoming requests. The next two # directives control the behaviour of the threads and processes. # # # MaxRequestsPerChild: the number of requests each child process is # allowed to process before the child dies. The child will exit so # as to avoid problems after prolonged use when Apache (and maybe the # libraries it uses) leak memory or other resources. On most systems, this # isn't really needed, but a few (such as Solaris) do have notable leaks # in the libraries. For Win32, set this value to zero (unlimited) # unless advised otherwise. # # NOTE: This value does not include keepalive requests after the initial # request per connection. For example, if a child process handles # an initial request and 10 subsequent "keptalive" requests, it # would only count as 1 request towards this limit. # MaxRequestsPerChild 0 # # Number of concurrent threads (i.e., requests) the server will allow. # Set this value according to the responsiveness of the server (more # requests active at once means they're all handled more slowly) and # the amount of system resources you'll allow the server to consume. # #ThreadsPerChild 1 # broke the IO socket #Should be on 50 like below ThreadsPerChild 50 -----Original Message----- From: Perrin Harkins [mailto:[EMAIL PROTECTED]] Sent: Monday, February 04, 2002 10:10 AM To: Purcell, Scott; [EMAIL PROTECTED] Subject: Re: Speed of downloading problem. > I have Apache/mod_perl installed on a NT box, and I am allowing customers to > do downloads of High-Resolution assets. My problem is the speed of downloads > is about 1/3 slower than the same box running IIS. Can you post your httpd.conf? Or at least the parts of it about threads and processes? It is possible that Apache is just not that fast on NT. NT support is experimental in the 1.3 series. > One thought here was to go to 2.0 You can't run mod_perl 1.x on Apache 2.0. Another thing you could try is having multiple servers. One could handle static requests and proxy the dynamic ones to mod_perl. I don't know if IIS knows how to do this or not, but there's probably something available for NT that does it. - Perrin
