Hacker News new | comments | show | ask | jobs | submit login

when i last used ec2, it was almost exclusively for async backend processes. in those cases, high throughput is important, but latency is not a factor in the same way. If there's a 300ms delay talking to the system from the outside world, it's no big deal.

that said, netflix seems to have solved the IO issue with ec2. I'd be curious to know more about their findings.




Main way we solve IO issues: We don't rely on EBS -- most data is stored on the local drives using Cassandra.

For cache throughput, our cache library adds zone affinity to memcache, so the clients are hitting the cache in the same zone first.

Also, we're now exploring their SSD options (http://techblog.netflix.com/2012/07/benchmarking-high-perfor...)




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: