A few days ago, the new C4 instances were made available to seven AWS regions around the globe:
- US East (Northern Virginia)
- US West (Oregon)
- Europe (Ireland)
- Asia Pacific (Tokyo)
- US West (Northern California)
- Asia Pacific (Singapore)
- Asia Pacific (Sydney)
Amazon Web Services Blog: Now Available – New C4 Instances
| Instance Name | vCPU Count | RAM | Network Performance | Dedicated EBS Throughput | Linux On-Demand Price |
| c4.large | 2 | 3.75 GiB | Moderate | 500 Mbps | $0.116/hour |
| c4.xlarge | 4 | 7.5 GiB | Moderate | 750 Mbps | $0.232/hour |
| c4.2xlarge | 8 | 15 GiB | High | 1,000 Mbps | $0.464/hour |
| c4.4xlarge | 16 | 30 GiB | High | 2,000 Mbps | $0.928/hour |
| c4.8xlarge | 36 | 60 GiB | 10 Gbps | 4,000 Mbps | $1.856/hour |
※ The prices listed above are for the US East (Northern Virginia) and US West (Oregon) regions.
C4 instances for AMIMOTO are currently pending, but we have done some tests to it and the results were fantastic:
We’ve tried a testing environment where US East (Northern Virginia) was selected as the region and c4.large as the corresponding instance.
In the WordPress 4.1 installation, Nginx Cache Controller plugin was activated and Theme Unit Test was imported.
Pingdom Website Speed Test was used to measure the result from Dallas, Texas:
| Perf. grade | Requests | Load time | Page size |
|---|---|---|---|
| 75/100 | 24 | 467ms | 324.2kb |
The acquisition of html has been completed in 100ms, which was a very good result. The request number by ab is 1000, and the concurrency level is 100.
In order to eliminate the influence of the network, the Amimoto AMI instance was executed by creating an instance on the same AZ and AZ that are movable.
$ ab -n 1000 -c 100 http://54.164.136.129/
This is ApacheBench, Version 2.3 <$Revision: 655654 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/
Benchmarking 54.164.136.129 (be patient)
Server Software: nginx
Server Hostname: 54.164.136.129
Server Port: 80
Document Path: /
Document Length: 55248 bytes
Concurrency Level: 100
Time taken for tests: 1.414 seconds
Complete requests: 1000
Failed requests: 0
Write errors: 0
Total transferred: 55799954 bytes
HTML transferred: 55604208 bytes
Requests per second: 707.26 [#/sec] (mean)
Time per request: 141.391 [ms] (mean)
Time per request: 1.414 [ms] (mean, across all concurrent requests)
Transfer rate: 38540.15 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 6 70.4 1 1000
Processing: 2 79 202.0 6 1412
Waiting: 0 4 31.8 1 614
Total: 2 85 212.3 7 1414
Percentage of the requests served within a certain time (ms)
50% 7
66% 9
75% 13
80% 26
90% 214
95% 609
98% 1003
99% 1015
100% 1414 (longest request)
In Requests per second, the result was 707, and this is a huge benefit from NGINX Reverse Proxy.
The measurement below is the result of NGINX Cache Controller being turned off in the same instance (c4.large):
$ ab -n 1000 -c 100 http://54.164.136.129/
This is ApacheBench, Version 2.3 <$Revision: 655654 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/
Benchmarking 54.164.136.129 (be patient)
Server Software: nginx
Server Hostname: 54.164.136.129
Server Port: 80
Document Path: /
Document Length: 55248 bytes
Concurrency Level: 100
Time taken for tests: 129.349 seconds
Complete requests: 1000
Failed requests: 0
Write errors: 0
Total transferred: 55442000 bytes
HTML transferred: 55248000 bytes
Requests per second: 7.73 [#/sec] (mean)
Time per request: 12934.896 [ms] (mean)
Time per request: 129.349 [ms] (mean, across all concurrent requests)
Transfer rate: 418.58 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 1 0.3 1 4
Processing: 146 12413 2622.8 12903 19199
Waiting: 143 12410 2622.8 12900 19196
Total: 146 12414 2622.9 12904 19200
Percentage of the requests served within a certain time (ms)
50% 12904
66% 12957
75% 12992
80% 13015
90% 13122
95% 13860
98% 16584
99% 17593
100% 19200 (longest request)
With NGINX Cache Controller being switched off, you may notice that there was a significant drop in requests per second, which was now at 7.7.
C4 family is only available to Amimoto HVM version. For clients interested in applying for the latest Amimoto C4 instances, contact us or directly check out the AWS Marketplace for WordPress Powered by AMIMOTO (HVM).