This is from memory many years ago, so minor details might be off: If these large requests are very infrequent, and not something you can segregate out (to send to an HTTPD with fewer threads and overall lower transaction volume), you might want to consider more smaller thread
workers and a limit to the number of requests a given worker will process, so that process would be recycled before all the threads hit that big response. Rick Houser Web Engineer From: Campbell, Lance [mailto:lance@xxxxxxxxxxxx]
EXTERNAL EMAIL Apache 2.4 Worker MPM I am using this configuration for Worker MPM: <IfModule mpm_worker_module> ServerLimit 90 StartServers 10 MaxRequestWorkers 2048 MinSpareThreads 25 MaxSpareThreads 75 ThreadsPerChild 25 </IfModule> Apache has created 12 processes. Apaches memory consumption slowly increases but never goes down. Currently Apache is using 423M and the average Process size is 35.3M. When I look at the Apache access log
I see an enormous number of requests coming across my terminal. Should I change my settings? I am concerned that at some point I am going to run out of memory.
Since I started writing this email Apache is now up to 426M and the average process size is at 35.5M. Thanks, Lance |