Question
Which MPM should I choose?
Answer
The following is a brief description of the available MPM modules configurable through EasyApache:
| MPM | Description |
|---|---|
| worker | The worker MPM causes Apache to fork multiple processes to ensure that a single crash does not terminate the entire Apache service. Each forked process creates multiple threads, and a listener thread that listens for incoming connections. This configuration enables the server to handle multiple requests concurrently. |
| event | The event MPM processes a single HTTP request across multiple threads. It dedicates threads to handle active connections and uses an event-driven mechanism to manage keep-alive requests efficiently. This behavior ensures that threads are instantly available after a request is completed. We recommend the event MPM for users with occasional concurrent requests, or those that require long keep-alive timeouts. |
| prefork (default) | The prefork MPM forks additional processes in advance of incoming requests. When Apache receives a request, the server can respond promptly because an Apache process is already available to handle it. If a problem occurs with an individual process, Apache can terminate that process without affecting the others. Since the prefork MPM is not threaded, each child process can handle only one request at a time. The system queues concurrent requests and the MPM processes each request as resources become available. |
Additional resources
Multi-Processing Modules: MPMs
Comments
0 comments
Article is closed for comments.