Tag Info

Hot answers tagged

9

At first, the client requests will get queued, until there is a process/thread that gets free on the apache server. So, the clients will see a delay in loading the page. See the MaxClients parameter documentation for more information. When placed in the backlog queue, the client request can eventually time out on the client side. Then the user will see ...


2

What you can raise MaxRequestWorkers to depends on how much RAM each of your httpd / apache processes takes up. If each one takes up 50MB (just picking a random number), then every 20 request workers you have in use at once (i.e. concurrent connections) will take up 1GB. So in that example, you could have at most 8GB * 20 = 160 MaxRequestWorkers. However, ...


2

Recognize that Ubuntu 14.04 uses Apache 2 with PHP running through an mpm_prefork module, of which an editable file is in /etc/apache2/mods-enabled/mpm_prefork.conf. Also, recognize that starting in Apache 2.4, MaxClients is now renamed as MaxRequestWorkers, and so any documentation regarding MaxClients needs to be switched to MaxRequestWorkers. Stop the ...


2

I suspect that you have several issues here that are stacking up and causing problems. Disk i/o is fragmented, and probably inefficient. OPTIMIZE TABLE on each of your tables should sort that out and help a bit. Memory is tuned horribly, likely causing issues with having to swap frequently. Slow queries - this is the big suspect for your high CPU usage. ...


2

What's the question here? You don't seem to be comparing apples-to-apples. So I'm not sure if you just want this system to run like your other systems, or if you really care about the cause of the performance difference. You could obtain another of the server model and SKU that you're familiar with. You could use the same type of disks you used in ...



Only top voted, non community-wiki answers of a minimum length are eligible