I have created EC2 instances of Bitnami and Amimoto, and tried to compare their performance.
As test data, WordPress 3.4.1 Japanese version imported English version of the Theme Unit Test Data .
In Amimoto, WP Booster and Nginx Cache Controller has been introduced.
The instance type that I use is t1.micro of EC2.
The AMI specs are as follows:
- Amimoto : ami-cab507cb ( CentOS 6.2, Nginx 1.2.2, PHP 5.3.14, Percona 5.5.24 )
- Bitnami : ami-06ff4c07 ( Ubuntu 12.04, Apache 2.2.22, PHP 5.3.13, MySQL 5.5.21 )
Measuring Result by Pingdom Tools
The result was measured using Pingdom Tools which computes the load time of a website just like below.
The total load time of Amimoto and WP Booster is 1.52 seconds, and in Bitnami, the time is 2.17 seconds.
The major factor is that WP Booster delivers images with the CDN.
Load Test with a Simple ab (Apache Bench) Command
Using the ab command, I’ll try to put a load on the top page.
Run ab -n 100 -c 10 (100 is total number of requests, 10 is the number of concurrent connection), and the results are as follows.
| / | Time taken for tests |
Requests per second |
Time per request |
Transfer rate |
Connect (mean) |
Processing (mean) |
Waiting (mean) |
Total (mean) |
|---|---|---|---|---|---|---|---|---|
| Amimoto | 0.922 seconds |
108.41 [#/sec] |
92.241 [ms] |
5020.70 [Kbytes/sec] |
14 [ms] |
74 [ms] |
13 [ms] |
88 [ms] |
| Bitnami | 98.771 seconds |
1.01 [#/sec] |
9877.068 [ms] |
47.84 [Kbytes/sec] |
14 [ms] |
4620 [ms] |
2503 [ms] |
4634 [ms] |
As measured by Requests per second, the value of Amimoto is 108.41 [#/sec], while that of Bitnami is 1.01 [#/sec], so the difference is almost 100 times.
Just for the record, run the command with 1,000 total requests and 100 concurrent connections, the number of process per second by Amimoto is 267.46 [#/sec].
With Bitnami, unfortunately, it was not able to be measured.
CPU usage while the load test was running is as follows.
The green line of i-7810f37b is Amimoto and the blue line of i-d810f3db is Bitnami.
You can see the CPU load of Bitnami is going up, but in Amimoto, it remains almost unchanged.
Even a powerless instance like that of t1.micro, when you use Amimoto and enable Nginx Cache Controller, it is not overloaded so much.