4 ms·
One thing is s3/gcs latency. On my last job we had a Go server running on ec2/gce and do some occasional read from s3/gcs (same, single region). We used to be r
by fishywang 9y ago
One thing is s3/gcs latency. On my last job we had a Go server running on ec2/gce and do some occasional read from s3/gcs (same, single region). We used to be running on ec2+s3 but later switched to gce+gcs for cost reasons (gcp only costs ~60% of aws' cost for our setup). But the thing we noticed was that when we were on aws reading ~10KB single file from s3 usually takes <100ms, occasionally hit 100ms+ but rarely hit >200ms. On gcp that's usually >100ms, sometimes hikes to >1s and rarely goes <100ms.
- boulos 9y agoDisclosure: I work on Google Cloud. Yeah, the underlying system is optimized for throughput (though we're working on small file latency). AWS clearly has a small file optimization and caching that we don't (yet). I often point people at Zach Bjornson's blogpost [1] since he compared all three providers and is a neutral third party. [1] http://blog.zachbjornson.com/2015/12/29/cloud-storage-performance.html http://blog.zachbjornson.com/2015/12/29/cloud-storage-perfor...