WordPress MU

with this typed at the command line:

ab -c 10 -n 100 http://my-blog.url.com/

(Hit that URL 100 times with 10 concurrent "users")

I get 3.8 requests per second

Tried the same with 30 concurrent users and still got 3.8/sec. but about 20% of connections were dropped and my server load went to almost 20.

This on a AMD Sempron 512 MB, with a few sites running in the background, load at 0.1-0.3. The URL I tried was a blog home page w/ 6-7 plugins enabled and ~99 mysql queries to build the page, so fairly heavy.

I have the object cache and eaccelerator installed, but not wp_cache yet.

Anyone wanna post some results from his server?

Apache bench should already be installed (comes with Apache) so you should be able to run the above command.

7.75 / sec.

when I try a "Hello World" home page of a blank, new blog with no plugins (56 mysql queries).

512 MB of RAM?

You might want to consider more.

MySQL will eat a LOT of it with MU.

Also look up the calling all large hosts thread here, and other mysql posts.

Lots of info floating around that may be of use.

I am aware of that, the production server(s) will have 1-2 GB I guess.

Anyway, I was merely looking for others running an apache bench test on their server, maybe with wp_cache installed (I couldn't get wp_cache running - yet), and post their results so we can compare hardware, and the performance with/without wp_cache.

are you running this on the machine that does serve the pages?

and what does this mean?

Complete requests:      100
Failed requests:        98
   (Connect: 0, Length: 98, Exceptions: 0)

Yes I ran it on the same server. But it should run from a different server as well

Almost all your requests failed, so your server probably couldn't handle the amount of concurrent queries (10, if you used "-c 10").

BUT there should be a difference in running locally or running from another server, I guess...

At least I expect apache to treat connections from localhost different then outside requests... i.e. I have mod_evasive, which block too many requests in a certain amount of time :-) (from the same ip)...

Completed requests: 100
Failed: 0

avg of .368 seconds per request.

Server Load is around 6 with a WPMU 1.0 blog with several plugins enabled.

Complete requests: 1000
Failed requests: 0

Requests per second: 12.53 [#/sec] (mean)
Time per request: 79.781 [ms] (mean, across all concurrent requests)

Hi,

Apache Bench disables any reverse proxy, so it doesn't show the true capacity of your server in this case.

I have a puny webserver (old AMD athlon, 512 MB RAM) serving dynamic pages (WordPress-based blogs).

Using apache bench, it can only serve 0.88 requests per second.

However, when the reverse proxy is utilized, my server suddenly able to serve 1000x more requests.

Here are the numbers :

MaTps 619.62, Tps 770.28, Resp Time 0.013, Err 0%, Count 18935
(here is the explanation of those numbers)

The benchmark command :
openload http://asiablogging.com 10

Note that this benchmark is executed from the same server, with OpenWebLoad taking up a sizeable chunk of CPU power for itself.
If done from other server(s), I suspect the numbers will be able to go up even further.

Hope someone find this useful.

Concurrency Level: 10
Time taken for tests: 0.23350 seconds
Complete requests: 100
Failed requests: 0
Write errors: 0
Total transferred: 3175500 bytes
HTML transferred: 3140900 bytes
Requests per second: 4282.66 [#/sec] (mean)
Time per request: 2.335 [ms] (mean)
Time per request: 0.234 [ms] (mean, across all concurrent requests)
Transfer rate: 132805.14 [Kbytes/sec] received

Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 0.0 0 0
Processing: 0 1 1.0 2 4
Waiting: 0 1 0.8 1 4
Total: 0 1 1.0 2 4

Percentage of the requests served within a certain time (ms)
50% 2
66% 2
75% 2
80% 2
90% 3
95% 3
98% 4
99% 4
100% 4 (longest request)

slicehost 256MB (the smalest slice) wpmu 2.7, eacellerator and nginx:

Server Software: nginx/0.6.34
Server Hostname: ****.no
Server Port: 80

Document Path: /
Document Length: 4676 bytes

Concurrency Level: 10
Time taken for tests: 12.48686 seconds
Complete requests: 100
Failed requests: 0
Write errors: 0
Total transferred: 488900 bytes
HTML transferred: 467600 bytes
Requests per second: 8.30 [#/sec] (mean)
Time per request: 1204.869 [ms] (mean)
Time per request: 120.487 [ms] (mean, across all concurrent requests)
Transfer rate: 39.59 [Kbytes/sec] received

Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 1.4 0 12
Processing: 272 1191 1583.4 456 5540
Waiting: 272 1191 1582.8 456 5540
Total: 272 1191 1583.5 456 5540

Percentage of the requests served within a certain time (ms)
50% 456
66% 532
75% 616
80% 3268
90% 4504
95% 5028
98% 5316
99% 5540
100% 5540 (longest request)