|
|
|
|
|
by twotwotwo
4955 days ago
|
|
- No one pick a host based on a single microbenchmark, please. Game out what your app would need to achieve your target performance level with what each host offers. Amazon still might lose (sounds like that happened with TripAdvisor) but at least you've made your decision a sane way. - For the best price, you'd want to use a reserved instance if this is a webserver, and perhaps a spot instance if it's a batch/HPC task. You'd want to use high-CPU instances if you really are all about quickly sorting 5M numbers. If your app is or might be come database-bound, DB perf's super key. - I'd love to hear more broadly about the practical differences between the clouds--whether anyone seems to be better at managing noisy neighbors than the next guy, network and I/O performance, etc. One CPU-bound task can't really be the end of it. |
|
Small: 6.5 cents/ecu-hr
Small, 1yr: 4.7 cents/ecu-hr
Small, spot: 1 cent/ecu-hr
High-CPU: 3.3 cents/ecu-hr
High-CPU, 1yr: 1.9 cents/ecu-hr
High-CPU, spot: 0.56 cents/ecu-hr
If RAM matters, high-CPU (7G, or 3.5/core) > Small (1.7G) > EC2 Micro and Joyent extra-small (~0.5G). Again, don't rely too much on figures like these; look at all your needs (not just performance, everything) and try to figure out what'll work for you.