Multi-processing modules in apache

-
The Apache HTTP Server is designed to be a powerful and flexible web server that can work on a very wide variety of platforms in a range of different environments. Apache2 comes with 2 multi processing modules(MPMs) which are responsible for binding to network ports on the machine, accepting requests, and dispatching children to handle the requests.:
1. Prefork
2. Worker
What is the difference between this two?
Prefork MPM uses multiple child processes with one thread each and each process handles one connection at a time.
Worker MPM uses multiple child processes with many threads each. Each thread handles one connection at a time.
On most of the systems, speed of both the MPMs is comparable but prefork uses more memory than worker.
Which one to use?
Websites that need a great deal of scalability can choose to use a threaded MPM like worker (because of low memory usage) while sites requiring stability or compatibility with older software can use a prefork (prefork is more safe if using libraries which are not thread safe).
Running following command to check which MPM on linux :
#httpd -V |grep MPM
or
#apachectl -V |grep MPM

Comments

Post a Comment

Popular posts from this blog

Web Servers Load balancing with HAProxy

-
HAProxy is a free, very fast and reliable solution offering  high availability , load balancing , and proxying for TCP and HTTP-based applications. It is particularly suited for very high traffic web sites and powers quite a number of the world’s most visited ones. See more at  http://haproxy.org This tuturial, I use hostname and ip as follows: 10.11.218.250 (haproxy) 10.11.218.251 (srv-web01) 10.11.218.252 (srv-web02) Installing HAProxy server #yum install haproxy [RedHat Systems] #apt-get install haproxy [Debian Systems] Configuring HAProxy Server Opening the main HAProxy configuration file ‘/etc/haproxy/haproxy.cfg’ and editing the following content: #---------------------------------------------------------------- # Global settings global # need to: # to have these messages end up in /var/log/haproxy.log you will # # by adding the '-r' option to the SYSLOGD_OPTIONS in # 1) configure syslog to accept network log events. This i
Read more

Redirect all unencrypted traffic to HTTPS in Apache

-
To redirect all HTTP traffic to HTTPS administrators are encouraged to issue a permanent redirect using the 301 status code. When using Apache this can be achieved by a setting such as the following in the Apache VirtualHosts config: <VirtualHost *:80> ServerName example.com Redirect permanent / https://example.com/ </VirtualHost>
Read more

Using nginx as http load balancer

-
Image
Load balancing across multiple application instances is a commonly used technique for optimizing resource utilization, maximizing throughput, reducing latency, and ensuring fault-tolerant configurations. Nginx is a very efficient HTTP load balancer to distribute traffic to several application servers and to improve performance, scalability and reliability of web applications. Nginx Load balancing methods The following load balancing mechanisms (or methods) are supported in nginx: round-robin least-connected ip-hash See detail at http://nginx.org/en/docs/http/load_balancing.html Initialization Nginx Load Banlancing In this tutorial I use any hostname and ip addresses as follows: srv-lb01 (10.11.218.250) (Nginx load balancer) srv-web01 (10.11.218.251) ( Web server) srv-web02 (10.11.218.252) ( Web server) srv-web03 (10.11.218.253) ( Web server) Note: pointing nginx.vn to 10.11.218.250 (Replace nginx.vn with your real site name) Default load balancing c
Read more