EC2 region benchmark

1 minut läsning

Ever thought about what region to use for what audience? Lot’s of people must have but they keep their findings to themselves from what I can tell.

Obviously if you want to target Japan, put you site in the Tokyo region. But if you want to target Vietnam or Thailand, like the client who put me up to crude benchmark did, then you may be at a loss.

I have a PhD but this is so unscientific. Interesting perhaps, nonetheless.

I set up the same site on a number of different Regions in the AWS cloud. Then tested the first uncached page load using the very helpful webpagetest.org. Webpagetest.org let’s you test your site as a browser client from a number of different sites accross the globe. Unfortunately not Vietnam and not Thailand. You can even script it if you want.

The resulting graph looks like what you would get from hitting F12 in Chrome and opening the network tab.

Here are my results.

<td colspan=2></td><td colspan=3>Access point</td><td colspan=2></td><td rowspan=5>Region</td>
JiangsuTokyoAmsterdam
Ireland (eu-west)55 s8 s4 s
Virginia (us-east)10 s6 s5 s
Oregon (us-west)8 s5 s6 s
Singapore (ap-southeast)16 s4 s9 s
Tokyo (ap-northeast)11 s29 s5 s

Disclaimer: Singapore is the original site and has some overhead, like SSL-encryption. I only did this once so that hardly qualifies as statistics. But it gives you an idea about what to expect when you launch a site intended for certain locality.

Someone should do an extensive benchmark. Maybe I should. Btw, take at Google Page Speed if you haven’t already.

Uppdaterades:

Lämna en kommentar