	Too many Apache processes

	Cheap web hosting

	Windows web hosting

	Linux web hosting

	Unrestricted hosting

	Ecommerce web hosting

	Virtual server VPS

	Reseller hosting

	by US State

	by US City

	Web Hosting coupons

	VPS coupons

	Articles

	Cheap dedicated servers

	Best dedicated servers

	Windows dedicated servers

	Linux dedicated servers

	Unrestricted server

	dedicated managed server

	dedicated server unmetered

	by US State

	by US City

	Dedicated server coupons

	Articles

	Cheap colocation hosting

	Unrestricted Colocation

	by US State

	by US City

	Coupons Promotion

	Articles

	Domain Registration

	SSL Certificate

	Website Statistics

	Merchant account

	Control panel

	WebSite monitor

	Intel Servers

	AMD servers

	SCSI Servers

	Cheap Servers

	Web hosting company

	Dedicated Hosting

	Colocation hosting

	Web Hosting Services

	Server manufacturer

	Reviews

So you want to know how you decide what web host is best!

What is 1Mbps 95th percentile ?

Top 10 Dedicated servers May 2010

Westmere Dedicated server the best deal

Using CMS to create Websites

Top 10 Dedicated Servers March 2010

Control Panel Benefits

Top 10 Dedicated servers January 2010

More Articles

Ring the Christmas Bells with Infrenion Networks 50% Discount!

WebHost.UK.Net: offering web hosting great deals this Christmas.

Action Web Group Introduces The All New RubberBand Plan To Take The Place Of Unlimited Web Hosting!

Vision Helpdesk Christmas Madness is back! HO-HO-HO Huge Discounts!

Codero Names Jonathan Ewert as President and CEO

Lunarpages Boosts Reseller Plan

More News

Too many Apache processes

Question:

Too many Apache processes

Too many Apache processes, What I have to do?

Answer: Too many Apache processes

A common misconception is that if more is good, a lot more must be great. It is easily possible to have too many processes open and take a productive machine from being efficient to being as useful as a brick in a hurry. Often if a server is seeing a large amount of traffic neophite administrators will increase the MaxClients and MinSpareServers to astronomical levels. In only very rare circumstances is setting MaxClients over 200 actually necessary. If you have a good balance of MaxSpareServers, MinSpareServers, MaxClients and KeepAlive settings you can push a huge amount of traffic and still handle new connections. Let�s look at a few examples.

Say you have a server that makes 100 new connections per second and MaxClients is set to 200. With KeepAlive off (the default) you shouldn�t have any trouble. As each file is sent to the client the connection is closed and freed up for other clients to use. This is fine as long as the data can be sent at least as fast as new connections are established. If you have a very content rich site with lots of large graphics this may become problematic. You could run into conditions where new connections are occuring faster than you can send the data across multiple streams to a single client. Often administrators will try to compensate by increasing MaxClients to sometimes astronomical levels. Even a dual Xeon will have a hard time keeping up with thousands of clients while processing SQL queries at the same time. This will have the effect of turning your shiny new server into a pile of goo in no time.

This is where KeepAlives can keep your server online. KeepAlive works with browsers newer than IE4 and Netscape 5. Even if a user shows up with one of these now antiquated browsers your server will be visible, that user will just consume more resources on your server. KeepAlive allows a client to handle multiple data streams (html documents, graphics, Flash animations, etc.) through one TCP/IP connection. This acts more like a multiplier since each file no longer needs to open it�s own connection. Effective use of KeepAlive and MaxClients can have a dramatic effect on how well your server performs. You can control the number of requests a single session is permitted with the MaxKeepAliveRequests directive (the default of 100 is reasonable) and the duration a client is allowed to keep a session open with the KeepAliveTimeout directive. On a busy server I tend to turn the KeepAliveTimeout directive down and the MaxClients up but ONLY if the back end server can keep up with the web server. If both SQL and Apache are running on the same server make sure your bottleneck isn�t actually the SQL server or you�ll be right back to square zero.

Related Questions

Redirecting Email with Cpanel Redirecting Email with Cpanel Server Management

Create a Subdomain with Cpanel How to create a Subdomain with Cpanel Server Management

Ban IP address with Iptable how can i ban that Ip address from the server? Server Management

How to verify that my mailserver is not an open relay How to verify that my mailserver is not an open relay Server Management

Too many Apache processes Too many Apache processes, What I have to do? Server Management

How to change my Linux dedicated server route table How to change my Linux dedicated server route table Server Management

Apache will not start If your apache webserver will not start, there are several things which you can check Server Management

How can I reset my password on my Plesk Linux server? How can I reset my password on my Plesk Linux server? Server Management