Series: Apache Performance Tuning

Apache by default logs data directly to log files. While this isn't a bad thing, it is not your only option. Both Apache 1.x and Apache 2.x bring with them the option of enabling something called "Piped Logging", though cPanel will only allow you to enable it for version 2.x.

Before we get into the details of Apache tuning, we need to understand what happens when a VPS server or Dedicated server goes unresponsive due to a poorly optimized configuration.

Our previous article in this series focused on defining and fitting MPM to match your environment.  Building from our last tutorial we will be discussing specific details on how to adjust the previously mentioned Apache configuration directives on the various types of Liquid Web VPS servers as well as Core managed servers.  

How directives behave and which directives are mainly available hinges on the loaded MPM. As discussed in our previous series, MPM is short for MultiProcess Modules, and they determine the basis for how Apache addresses multiprocessing. Using our last article on Apache MPM Modules as a springboard, we will use this section to cover the following subsections:

The keystone for understanding Apache server performance is by far the Multiprocessing Modules (MPMs). These modules determine the basis for how Apache addresses multiprocessing. Multiprocessing means running multiple operations simultaneously in a system with multiple central processing units (CPU Cores).