Apache which mpm

Now run the apache binary with the "l" option. It provides a list of all the modules that have been compiled into apache. In the above output it can be see that worker. So mpm worker is being used. The Prefork MPM creates multiple child processes each of which handle a request. In conclusion, the Apache event MPM increases the performance of your Apache server, allowing it to serve more requests with less memory.

Bitnami stacks use this configuration by default for virtual machines and cloud images. Understand the Apache event MPM Apache supports three different Multi-Processing Modules MPMs that are responsible for binding to network ports on the machine, accepting requests, and dispatching children to handle the requests.

Worker: It uses multiple child processes with many threads each. The amount of data transferred is much higher. The transaction rate is higher and there are less failed transactions. It is also important that the load time in the first case could be very different for different tests, as it depends on the number of free child processes. The Transaction rate is much higher in the second case. The Longest transaction is similar to the Shortest transaction.

Additionally, attempting to scale up in the count of prefork child processes, you'll easily suck down some serious RAM. Even then, consider using FastCGI and php-fpm.

Worker spins off some child processes, which in turn spin off child threads; similar to prefork, some spare threads are kept ready if possible, to service incoming connections. This approach is much kinder on RAM, since the thread count doesn't have a direct bearing on memory use like the server count does in prefork. It also handles concurrency much more easily, since the connections just need to wait for a free thread which is usually available instead of a spare server in prefork.

Don't use if: You really can't go wrong, unless you need prefork for compatibility. However, note that the treads are attached to connections and not requests - which means that a keep-alive connection always keeps a hold of a thread until it's closed which can be a long time, depending on your configuration.

Which is why we have.. The big difference is that it uses a dedicated thread to deal with the kept-alive connections, and hands requests down to child threads only when a request has actually been made allowing those threads to free back up immediately after the request is completed. This is great for concurrency of clients that aren't necessarily all active at a time, but make occasional requests, and when the clients might have a long keep-alive timeout.

The exception here is with SSL connections; in that case, it behaves identically to worker gluing a given connection to a given thread until the connection closes. Use if: You're on Apache 2. Everyone likes threads! In today's world of slowloris , AJAX, and browsers that like to multiplex 6 TCP connections with keep-alive, of course to your server, concurrency is an important factor in making your server scale and scale well.

Apache's history has tied it down in this regard, and while it's really still not up to par with the likes of nginx or lighttpd in terms of resource usage or scale, it's clear that the development team is working toward building a web server that's still relevant in today's high-request-concurrency world. Briefly: if you on 2. As of February , the Apache 2. See the Limitations section. The issue is that, as a proxy, the worker cannot tell where the end of the response is, and will be forced to wait until the entire response is seen before returning control to the listener.

For this reason, it seems that using the Worker model may be best for when apache is used as a proxy. It is not really clear to me if there are advantages to the event model in a proxy environment, but perhaps there are.

Mostly depends on which Apache modules you want to use. Apache is the most popular web server for Linux web servers. At the initial level the System administrator works with Apache. Both have their own working type.

Below is some basic details about both MPM and there working. Prefork MPM launches multiple child processes.