Morgan has asked me to do some testing on our servers performance to show to our clients. This blog post will contain the results. All test were performed from a Rackspace Cloud Server in the Chicago datacenter to give a bit of distance from our DFW servers.
The first thing we need to know, is how long does it take internet traffic to get to our servers and back. This is greatly variable on the end users geographic location. To connect to our web servers your web browser must make at least two round trips to the server to start getting the page. One to set up the connection, and one to get the page.
Using the standard network tool ping I ran a test from my test server to one of our web servers.
# ping -c 100 rewhosting.com
--- rewhosting.com ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 99188ms
rtt min/avg/max/mdev = 22.791/23.353/26.211/0.475 ms
So from this we can see all future test will be at least 23ms long. ms is milisecond, there are 1000 in a second.
The next thing to test is our DNS server speed. DNS is normally cached by your local ISP for you and makes for very quick lookups if they already know the answer. But in a worst case, they will need to hit one of our DNS servers.
I wrote a little script to do a DNS lookup 100 times at each of our nameservers and report the results. NS2 is a little closer to my Chicago test server, and so is a bit faster than the base ping time above,
Now lets test the speed of Apache serving a basic HTML page. Each of our servers has a page available at its IP address. EG: http://220.127.116.11/
For this I will use a tool called ab, the Apache HTTP server benchmarking tool. I set ab to make 10 requests at a time, and make 1000 requests total per server.
pic2.rewhosting.com Time per request: 54.472 [ms] (mean)
pic3.rewhosting.com Time per request: 55.465 [ms] (mean)
pic4.rewhosting.com Time per request: 62.660 [ms] (mean)
web6.rewhosting.com Time per request: 54.575 [ms] (mean)
web9.rewhosting.com Time per request: 54.516 [ms] (mean)
web11.rewhosting.com Time per request: 54.958 [ms] (mean)
web12.rewhosting.com Time per request: 66.611 [ms] (mean)
web14.rewhosting.com Time per request: 54.632 [ms] (mean)
web15.rewhosting.com Time per request: 57.359 [ms] (mean)
web16.rewhosting.com Time per request: 54.773 [ms] (mean)
web17.rewhosting.com Time per request: 55.056 [ms] (mean)
web18.rewhosting.com Time per request: 54.678 [ms] (mean)
web19.rewhosting.com Time per request: 55.496 [ms] (mean)
web20.rewhosting.com Time per request: 54.605 [ms] (mean)
web21.rewhosting.com Time per request: 55.066 [ms] (mean)
web23.rewhosting.com Time per request: 56.577 [ms] (mean)
web24.rewhosting.com Time per request: 54.674 [ms] (mean)
web25.rewhosting.com Time per request: 54.792 [ms] (mean)
web-42-01.rewhosting.com Time per request: 56.531 [ms] (mean)
web-42-02.rewhosting.com Time per request: 54.931 [ms] (mean)
web-42-03.rewhosting.com Time per request: 55.378 [ms] (mean)
web-42-04.rewhosting.com Time per request: 55.128 [ms] (mean)
web-42-05.rewhosting.com Time per request: 56.488 [ms] (mean)
web-42-06.rewhosting.com Time per request: 55.442 [ms] (mean)
web-42-07.rewhosting.com Time per request: 60.630 [ms] (mean)
web-42-08.rewhosting.com Time per request: 55.098 [ms] (mean)
web-42-09.rewhosting.com Time per request: 56.310 [ms] (mean)
web-42-10.rewhosting.com Time per request: 54.790 [ms] (mean)
web-42-11.rewhosting.com Time per request: 54.379 [ms] (mean)
web-42-12.rewhosting.com Time per request: 54.211 [ms] (mean)
web-42-13.rewhosting.com Time per request: 54.264 [ms] (mean)
IDX Images CDN
I'll again use ab to test the speed of the CDN used for IDX Photos. This is powered by Akamai and Rackspace.
The image used in this test is from a Calgary condo. https://9b00cf3e94b1da815385-784ad96279f01dfaf51af989e8f8f0cf.ssl.cf1.rackcdn.com/c3644659-condo-townhouse-1cnzw34-o.jpg
Akamai has edge locations for its CDN all over the place, so there is likely one very close to you. Again, I'm testing from a Cloud Server in Chicago.
Time per request: 26.621 [ms] (mean)