Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have just started to move our infrastructure to Amazon's AWS (EU West). Since we started the move we have started seeing some quite substantial spikes in network latency. Our setup is quite simple, we are running two/three web servers (large instances) behind a ELB and a RDS (XL instance) instance to server the web servers.

Our response time now ranges from abysmal to OK, today's values: 427 ms [London, UK] - 1,642 ms[London, UK] (values from Pingdom). With our previous provider (same setup, traditional managed hosting) we were used to seeing around 200 - 300 ms. Is there anything we can do to improve the response time or is this something that we have no control over.

I read about the problems Amazon seemed to have in Jan 2010 ( however haven't heard anything since thus assumed it was a brief period where this happened.

What do you guys think, is there something I can do or is it the penalty you have to use for Amazon's flexibility?

Thanks for your help.

share|improve this question

one solution can be that try to make testing server in all of the four zones, that you have available with you. and check that which zone's server has the least latency, then migrate all of your instance to that zone. (and remember to keep all of your server in one zone, to minimize latency among the servers.)

share|improve this answer
Doesn't that mean that if that particular zone goes down, all my services will be down as well? – luxerama Nov 12 '11 at 14:56
yes, it does. But that is Very Very rare case :) . at worst anything can happen. – Farhan Nov 12 '11 at 14:59

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.