Apache Performance

Apache is defined as being an general purpose web server, on that is very versatile, flexible, customizable, and yet powerful and secure. For this reason alone, it is easy to understand that there are many ways of fine tuning Apache to work at maximum efficiency for each individual who uses it. Although they may not help everybody, here are some useful modules and tips to get Apache running where it should be.

First off, security is always the most important aspect of a web server. Apache comes as a very secure server, however as someone installs tons of modules onto Apache, naturally it will become less and less secure. People have a mistaken mindset of the more modules the better. They think that more modules means more features and flexibility, but this is not the case. Half the modules that these people install will never even be used once and only create a security risk. Why? Because these modules aren’t written by the Apache developers, they are made by third parties, meaning who knows who could have code or potential ways of accessing them. The fact of the matter is that it is important to keep as few of modules running as possible. It is important to try and only run necessary modules, ones that are used frequently.

On that note, two modules that can be installed to increase the security of the Apache web server are named “mod_security” and “mod_dosevasive”. Mod_security adds intrusion detection and prevention features to the Apache Web Server. It has built-in functions to prevent various types of attacks such as command execution, directory traversal, SQL injection, etc, and is a very useful tool for managing the security of the Apache web server. Mod_dosevasive can detect web attacks, such as HTTP DoS or DDoS attack or brute force attack, and then take necessary steps to ensure that the attacks do not bring the server down.

As far as increasing performance, there are a few general tips that are good to know. Just as with an operating system (especially Windows XP), having plenty of RAM only helps. Unlike modules, the more RAM the better is true in every case. If the server doesn’t have enough RAM, Apache can actually ruin the server and make it inaccessible from the outside. Obviously, this is a very undesirable situation and it is wise to have at least 1GB of RAM, preferably more. A second performance note only relates to those who allow file downloads off their servers. For downloads, it is wise to not let Apache handle them but rather to have the thttpd module installed and handle such requests.

Hopefully after following these simple steps and recommendations every Apache run server can run just a little bit smoother and a little bit better. They are not difficult to do by any means, but all the little things count and add up to make Apache run faster and safer.