Apache performance optimization (4)
The following is the default configuration section of prefork:
StartServers 5 //
MinSpareServers 5 //The minimum number of idle processes is set.
MaxSpareServers 10 //Set the maximum number of idle processes. If the number of idle processes is greater than this value, Apache will automatically kill some redundant processes. Do not set this value too large, but if the value is smaller than MinSpareServers, Apache will automatically adjust it to MinSpareServers+1. If the site load is heavy, consider increasing both MinSpareServers and MaxSpareServers.
MaxClients 150 // MaxClients is the most important of these instructions. It sets the requests that Apache can handle at the same time and is the parameter that has the greatest impact on Apache performance. The default value of 150 is far from enough. If the total number of requests has reached this value (can be confirmed by ps -ef|grep http|wc -l), then subsequent requests will be queued until a processed request is completed. . This is the main reason why there are a lot of system resources left but HTTP access is very slow. System administrators can dynamically adjust this value based on hardware configuration and load conditions. Although theoretically the larger this value, the more requests that can be processed, Apache's default limit cannot be greater than 256 (derived from #define DEFAULT_SERVER_LIMIT 256 in 2.0). If this value is set to greater than 256, Apache will not start. In fact, 256 is not enough for sites with slightly heavier loads. In Apache 1.3, this is a hard limit. If you want to increase this value, you must search for 256 in src/include/httpd.h under the source code tree that was manually modified before "configure", and you will find the line "#define HARD_SERVER_LIMIT 256". Change 256 to the value you want to increase (such as 4000), and then recompile Apache. The ServerLimit directive was newly added to Apache 2.0, so that MaxClients can be increased without recompiling Apache. When using ServerLimit, just add a separate line here. If the value of ServerLimit exceeds 20000 as defined here, you must modify server/mpm/prefork/prefork.c #define MAX_SERVER_LIMIT 20000. Change 20000 to a larger value.
MaxRequestsPerChild 0 //Set the number of requests that each child process can handle. Each child process will be automatically destroyed after processing "MaxRequestsPerChild" requests. 0 means infinite, that is, the child process is never destroyed. Although the default setting of 0 allows each child process to handle more requests, setting it to a non-zero value also has two important benefits: it can prevent accidental memory leaks; it will automatically reduce the number of child processes when the server load decreases. number.
The working principle of worker is that the main control process generates "StartServers" sub-processes. Each sub-process contains a fixed number of ThreadsPerChild threads, and each thread processes requests independently. Likewise, in order not to spawn threads when requests come in.
The number of threads each process can have is fixed. The server will adjust to increase or decrease the number of processes based on load conditions. A single controlling process is responsible for the establishment of child processes. Each child process can create a fixed number of threads specified by ThreadsPerChild. Then, a separate thread listens for and handles incoming connections.
Apache always tries to maintain a spare or idle service thread pool. In this way, the client does not need to wait for the thread or process to be established before it can be processed. The number of processes initially created is determined by the StartServers directive. Afterwards, Apache detects the total number of idle threads in all processes, and creates or ends processes to keep the total number within the range specified by MinSpareThreads and MaxSpareThreads. Since this process is self-tuning, there is little need to modify the default values of these instructions. The maximum number of clients that can be processed simultaneously depends on the MaxClients directive, and the maximum number of processes established depends on the ServerLimit directive. ServerLimit multiplied by ThreadsPerChild must be greater than or equal to MaxClients.
The above is the content of Apache performance optimization (4). For more related content, please pay attention to the PHP Chinese website (www.php.cn)!

Hot AI Tools

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

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

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

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



To set up a CGI directory in Apache, you need to perform the following steps: Create a CGI directory such as "cgi-bin", and grant Apache write permissions. Add the "ScriptAlias" directive block in the Apache configuration file to map the CGI directory to the "/cgi-bin" URL. Restart Apache.

The steps to start Apache are as follows: Install Apache (command: sudo apt-get install apache2 or download it from the official website) Start Apache (Linux: sudo systemctl start apache2; Windows: Right-click the "Apache2.4" service and select "Start") Check whether it has been started (Linux: sudo systemctl status apache2; Windows: Check the status of the "Apache2.4" service in the service manager) Enable boot automatically (optional, Linux: sudo systemctl

This article introduces several methods to check the OpenSSL configuration of the Debian system to help you quickly grasp the security status of the system. 1. Confirm the OpenSSL version First, verify whether OpenSSL has been installed and version information. Enter the following command in the terminal: If opensslversion is not installed, the system will prompt an error. 2. View the configuration file. The main configuration file of OpenSSL is usually located in /etc/ssl/openssl.cnf. You can use a text editor (such as nano) to view: sudonano/etc/ssl/openssl.cnf This file contains important configuration information such as key, certificate path, and encryption algorithm. 3. Utilize OPE

To delete an extra ServerName directive from Apache, you can take the following steps: Identify and delete the extra ServerName directive. Restart Apache to make the changes take effect. Check the configuration file to verify changes. Test the server to make sure the problem is resolved.

This article will explain how to improve website performance by analyzing Apache logs under the Debian system. 1. Log Analysis Basics Apache log records the detailed information of all HTTP requests, including IP address, timestamp, request URL, HTTP method and response code. In Debian systems, these logs are usually located in the /var/log/apache2/access.log and /var/log/apache2/error.log directories. Understanding the log structure is the first step in effective analysis. 2. Log analysis tool You can use a variety of tools to analyze Apache logs: Command line tools: grep, awk, sed and other command line tools.

Apache connects to a database requires the following steps: Install the database driver. Configure the web.xml file to create a connection pool. Create a JDBC data source and specify the connection settings. Use the JDBC API to access the database from Java code, including getting connections, creating statements, binding parameters, executing queries or updates, and processing results.

There are 3 ways to view the version on the Apache server: via the command line (apachectl -v or apache2ctl -v), check the server status page (http://<server IP or domain name>/server-status), or view the Apache configuration file (ServerVersion: Apache/<version number>).

When the Apache 80 port is occupied, the solution is as follows: find out the process that occupies the port and close it. Check the firewall settings to make sure Apache is not blocked. If the above method does not work, please reconfigure Apache to use a different port. Restart the Apache service.
