Can we determine which server is good based on apache status?

Hi @yggitteam,

Since you are using a load balancer you can’t really tell which one is performing better in my opinion. Having said that, what you can do is optimize the one that you wish to use and then remove the other one.

You mentioned MPMs, a website really performs differently, in speed and everything depending on the MPM. What I usually like to use is MPM Event with PHP-FPM installed and OPcache enabled.

• Prefork: Each child process handles one connection at a time. This is the default mode for Apache.

• Worker: It uses multiple child processes with many threads each.

• Event: This MPM was designed to allow more requests to be served simultaneously by passing off some processing work to supporting threads and freeing up the main threads to work on new requests.

Let’s talk some facts, MPM Prefork is an old MPM and it’s quickly being replaced by both Worker and Event.:

• The default configuration for Apache and PHP in Linux systems is to use the prefork MPM with an embedded PHP interpreter. This is a very robust configuration but it means that Apache needs to spawn a separate process for every simultaneous request it wants to serve. Because every child process loads a PHP interpreter and associated libraries, this configuration takes a significant amount of memory.

MPM Event

• On high-traffic websites, an alternate MPM (the event MPM) is preferable because it has the ability to serve a large amount of requests while maintaining low memory usage. It does so by using threads to serve requests. It retains some of the stability of a process-based server by keeping multiple processes available, each with many threads so a thread potentially misbehaving would only affect all the other threads in the same process.

Basically, the best go to combination is MPM Event with PHP-FPM. That’s what everything is using, from cPanel servers to Plesk ones.

So, all in all, it doesn’t matter which server you’ll use but how you optimize it.

Regards, KFSys