How many connections/how much bandwidth can Apache handle?

Question

This is a request for pointers to good documentation/good articles. I'm looking for information on how many connections an Apache server can reasonably handle, and potentially how to load balance between multiple servers. I've done Google searches but it's harder for beginners to judge what are good docs.

Solution 1

Apache 1.3 had some nasty scalability limitations, but later versions are designed to scale with the hardware and operating system, making them the bottleneck rather than the web server itself. As always, though, it comes down to how you configure and tune it if you want uber performance. Each situation has its own demands, and they're documented here:

http://httpd.apache.org/docs/2.2/misc/perf-tuning.html

The above assumes you're serving static content, which is where Apache excels. If you run webapps behind it, that's your bottleneck, not Apache.

Solution 2

Unfortunately you'll be disappointed.

Apache's ability to handle connections (and indeed any other web server's) is limited by what the web application sitting on top of it is doing. If you're serving static pages, you will be able to serve a lot of requests with very little hardware.

Depending on the IO workload (Apache cannot work faster than the IO subsystem - install enough ram to cache your entire content, if you can), you will be able to fill up a gigabit network on any reasonable spec modern box.

Once you've filled a gigabit network, you'll have other things to worry about.

But the reasons that you really need load balancers are because your application slows down Apache and uses up the box's resources. Your application will not be infinitely fast, nor infinitely scalable. You'll need to address those issues.

Comments

[Dominic Rodger]

+1 - the apache documentation is likely to count as one of the "good docs"!

[Karl]

How is it disapointing that Apache can handle virtually unlimited bandwidth? I'd call that exciting.

[MarkR]

It's not unlimited bandwidth, just more than you care about. The web server should not itself create a bottleneck, which doesn't mean there won't be any anywhere else.