Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This question bothers me, and I do not think I am going to find the answer myself, so I thought it might be best to look for help.

When I do:

root@server1:~$ ab -n 20 -c 20

Duration is 4 seconds.

When I do (at the same time):

root@server1:~$ ab -n 10 -c 10
root@server2:~$ ab -n 10 -c 10

The combined duration is 2.5 seconds.

I should think the testserver isn't bothered by the location the requests are coming from, and I assume that testserver and server1 and server2 are not reaching their bandwidth cap (page isn't that heavy).

What is causing this? The answer will probably be really stupid, but I'll be happy regardless.

share|improve this question
What are the results if you use time ab? (ab is single-threaded. You may be CPU-limited.) – David Schwartz May 20 '12 at 21:50

There are some types of load where increased concurrency leads to performance drop. First come to my mind is sequential HDD read - you will get best overall performance if you have one thread of reading large file.

You need to investigate your server load and find the bottleneck.

Also 10 requests is too few to make any conclusions. Proper testing require you to monitor system in process and identify warm-up period for your system, when your load factors are stabilized. After warm-up you can run actual tests, and statistically research it's results to be sure that they are valid.

share|improve this answer
+1 for warmup suggestion. – SingleNegationElimination May 20 '12 at 17:39

When you run 1 process, the whole cpu is just working for that one process. (ok, and some for the kernel). When you run 2 processes, the kernel must switch between them, and on every switch it has to store some data to ram, and then retrieve it, which causes some overhead, so - more processes - more overhead.

Also, it depends how many apache workers are currently started. If there are 10 running, they just have to server the page. If you start 20 parallel connections, 10 more workes have to be started, which uses resources (or the requests have to wait).

share|improve this answer
The kernel is smart enough not to switch between processes so often that this switching causes appreciable overhead. – David Schwartz May 20 '12 at 21:48
situation where increasing concurrency reduces overall performance is an exception. More often performance is increasing with concurrency on logarithmic scale. – DukeLion May 21 '12 at 14:17
Yes, it increases performance as long as there are free resources. When <n> processes are using 100% of <n> CPUs, the performance starts falling because of overhead of switching between the (too many) processes. – mulaz May 21 '12 at 14:30

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.