4 ms·
Hm... the toy app you ported took about 5 seconds to respond. Slo-o-o-o-ow. Is that EC2 overhead? This is the kind of thing we were trying to avoid and ultimat
by tx 19y ago
Hm... the toy app you ported took about 5 seconds to respond. Slo-o-o-o-ow. Is that EC2 overhead?
This is the kind of thing we were trying to avoid and ultimately (again) decided on our own servers in a data center.
- DocSavage 19y agoI bet most of that response delay is from the autosuggest lookup against the dictionary. It seems to be querying every time you enter a letter, so if you quickly type a word, you'll be initiating multiple GET requests, each of which hits the DB.
- kirubakaran 19y agoIt is near instantaneous for me and I am in Seattle,WA,USA. I've heard from many sources that AWS is slow if you are outside the US. Someone even brought this up in the AWS dev conference and the Amazon guys just dodged it and gave a generic 'things are being improved' response. If http://www.instantwordsearch.com/ http://www.instantwordsearch.com/ look up is painfully slow but http://www.instantwordsearch.com/backstage.html http://www.instantwordsearch.com/backstage.html (statically served 103KB text) is very fast, then you can conclude that the problem is with my app. Otherwise it might be safe to blame EC2.
- tx 19y agoI am in Austin, TX and the front page took 5 seconds. I did not type anything or clicked anywhere. The problem with EC2 and other super-managed hosting solutions (Joyent comes to mind) is inconsistency: I am sure they're moving VMs around, and occasionally they end up on overloaded servers.
- wmf 19y agoBut I am equally sure that EC2 does not oversell CPU/RAM resources and does not move VMs around. I don't think Xen even supports memory overcommit.