How to tune Apache for better performance?
Jul 08, 2025 am 12:37 AMTo improve Apache performance, optimize configuration parameters are required. 1. Adjust KeepAlive parameters: Enable MaxKeepAliveRequests and set to 500 or higher, and set KeepAliveTimeout to 2~3 seconds to reduce connection overhead. 2. Configure the MPM module: Set StartServers, MinSpareServers, MaxSpareServers and MaxClients in prefork mode; set ThreadsPerChild and MaxRequestWorkers in event or worker mode to avoid excessive load. 3. Control memory usage: Set the MaxClients value according to the single-process memory usage and total memory, such as 2GB of memory set to 100. 4. Enable compression and caching: Compress files through mod_deflate and set the browser cache policy with mod_expires to speed up loading and reduce server pressure.
Apache is a widely used web server, but the default configuration is often not optimal. If you want to improve website response speed and reduce resource usage, tuning Apache configuration is one of the key steps .
Adjust MaxKeepAliveRequests and KeepAliveTimeout
KeepAlive can reduce the overhead of repeatedly establishing TCP connections, but if set up improperly, it will consume more memory and connections.
- MaxKeepAliveRequests : Controls the maximum number of requests that can be processed on a single connection, the default is 100. If the website has many static resources (such as images, CSS), it is recommended to increase this value appropriately, such as setting it to 500 or higher.
- KeepAliveTimeout : The time when the connection remains open when there is no new request, the default is 5 seconds. For sites with large visits, it is recommended to set it to 2~3 seconds to avoid long-term idle connections.
For example, you have a page that has 20 resources loaded. After turning on KeepAlive, these resources can be transmitted in a connection, which has significantly improved efficiency.
Control the number of concurrent connections: MPM module settings
Apache supports different MPM (Multi-Processing Module) modules, such as prefork
, worker
and event
. The tuning methods of different modules are slightly different:
-
If using
prefork
(suitable for modules that do not support thread safety, such as mod_php):- Set up the appropriate
StartServers
,MinSpareServers
, andMaxSpareServers
- Control
MaxClients
to not exceed server memory limit
- Set up the appropriate
-
If using
event
orworker
(more suitable for high concurrency):- Follow
ThreadsPerChild
andMaxRequestWorkers
- Make sure that the system load will not be too high due to too many threads
- Follow
Memory is the main limiting factor. For example, each Apache process takes up 20MB and the server has 2GB of available memory. Then, the maximum setting of
MaxClients
is about 100.
Enable compression and caching
Although this falls within the category of front-end optimization, Apache can help you automatically complete it:
- Use
mod_deflate
to compress HTML, CSS, and JS files - Set browser cache policies with
mod_expires
andmod_headers
This allows users to load pages faster while reducing server pressure.
For example:
<IfModule mod_deflate.c> AddOutputFilterByType DEFLATE text/html text/plain text/xml AddOutputFilterByType DEFLATE application/x-javascript application/javascript </IfModule>
Adding a configuration similar to the above can enable Gzip compression.
Basically that's it. Apache performance tuning does not require too complicated operations. The key is to make targeted adjustments based on your traffic model and server resources. Some parameters may require repeated testing to find the best value, but as long as you master these directions, you are already on the right path.
The above is the detailed content of How to tune Apache for better performance?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Software preparation I am using a virtual machine with CentOS-6.6, with the host name repo. Refer to the steps to install a Linux virtual machine in Windows, I installed JDK in that virtual machine, refer to the guide to installing JDK in Linux. In addition, the virtual machine is configured with a key-free login itself, and the settings for configuring key-free login between each virtual machine are referenced. The download address of Hadoop installation package is: https://mirrors.aliyun.com/apache/hadoop/common/. I am using hadoop 2.6.5 version. Upload the Hadoop installation package to the server and unzip [root@repo~]#tarzxv

NGINX is more suitable for handling high concurrent connections, while Apache is more suitable for scenarios where complex configurations and module extensions are required. 1.NGINX is known for its high performance and low resource consumption, and is suitable for high concurrency. 2.Apache is known for its stability and rich module extensions, which are suitable for complex configuration needs.

The steps to deploy a Joomla website on PhpStudy include: 1) Configure PhpStudy, ensure that Apache and MySQL services run and check PHP version compatibility; 2) Download and decompress PhpStudy's website from the official Joomla website, and then complete the installation through the browser according to the installation wizard; 3) Make basic configurations, such as setting the website name and adding content.

NGINX and Apache each have their own advantages and disadvantages, and the choice should be based on specific needs. 1.NGINX is suitable for high concurrency scenarios because of its asynchronous non-blocking architecture. 2. Apache is suitable for low-concurrency scenarios that require complex configurations, because of its modular design.

PHP code can be executed in many ways: 1. Use the command line to directly enter the "php file name" to execute the script; 2. Put the file into the document root directory and access it through the browser through the web server; 3. Run it in the IDE and use the built-in debugging tool; 4. Use the online PHP sandbox or code execution platform for testing.

Updating the Tomcat version in the Debian system generally includes the following process: Before performing the update operation, be sure to do a complete backup of the existing Tomcat environment. This covers the /opt/tomcat folder and its related configuration documents, such as server.xml, context.xml, and web.xml. The backup task can be completed through the following command: sudocp-r/opt/tomcat/opt/tomcat_backup Get the new version Tomcat Go to ApacheTomcat's official website to download the latest version. According to your Debian system

Reasons for system performance not recovered after uninstalling the Apache service may include resource occupancy by other services, error messages in log files, resource consumption by abnormal processes, network connection problems, and file system residues. First, check whether there are other services or processes before uninstalling with Apache; second, pay attention to the operating system's log files and find error messages that may occur during the uninstallation process; second, check the system's memory usage and CPU load, and find out abnormal processes; then, use the netstat or ss command to view the network connection status to ensure that no ports are occupied by other services; finally, clean up the remaining configuration files and log files after uninstallation to avoid occupying disk space.

The command to start the Apache service on macOS is sudoapachectlstart, and the configuration file is located in /etc/apache2/. The main steps include: 1. Edit the httpd.conf file, modify the Listen port such as Listen8080; 2. Adjust the DocumentRoot path to the personal directory such as /Users/your_username/Sites, and update the corresponding permission settings; 3. Use the sudoapachectlgraceful command to restart Apache to ensure that the configuration takes effect; 4. Enable the mod_deflate module to compress data to improve page loading speed.
