On 12/03/2012 20:36, Arianna Manlio wrote: > Hi, > > please, look at this mod-status output: > > Current Time: Monday, 12-Mar-2012 17:00:38 CET > Restart Time: Monday, 12-Mar-2012 16:58:11 CET > Parent Server Generation: 4 > Current Time: Monday, 12-Mar-2012 17:00:38 CET > Restart Time: Monday, 12-Mar-2012 16:58:11 CET > Parent Server Generation: 4 > Server uptime: 2 minutes 26 seconds > Total accesses: 22526 - Total Traffic: 79.3 MB > CPU Usage: u284.11 s22.21 cu.01 cs0 - 210% CPU load > 154 requests/sec - 0.5 MB/second - 3690 B/request > 8 requests currently being processed, 48 idle workers > > .__W_._____._..W_____.__.__._.___..C____W________...___WW.___W_W > ____..._...__................................................... > ................................................................ > ................................................................ > > At moment, MaxClients is 100. > Since I've 154 requests/sec, should I increase it to 150 or higher? > And what is the difference beetween 154 req/sec and 8 requests currently being > processed? > > Thankyou very much! > (you should post your configs)
If you use mpm_worker you can increase your MaxClients without going in outofmemory. "Usually" I calculate my apache parameters this way. Set ThreadsPerChild to 64 (default value). maxClients = (Available Memory / Child memory size) x ThreadsPerChild x K. where K = 0.85. Considering a burst of 200 concurrent requests (your case?), should increase MaxClients to 256 (if you have enough free memory, of course yes). MinSpareThreads = 128 (2 Childs = 128requests / 64 threadsPerChild) MaxSpareThreads = 256 (4 Childs = 256 Requests /64 threadsPerChild) i hope this helps you for future configurations -- Simone Caruso IT Consultant +39 349 65 90 805 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
