5 ms·
As far as the reason, you'd have to ask who works on AWS. For obvious reasons, we don't have direct access to the Amazon datacenter. As far as conclusive proof
by josegonzalez 15y ago
As far as the reason, you'd have to ask who works on AWS. For obvious reasons, we don't have direct access to the Amazon datacenter.
As far as conclusive proof is concerned, yes, we can't guarantee there wasn't a gravitational singularity that affected response time, but it's very likely that this was the case.
- rhizome 15y agoSo, "AWS happened to it," then?
- BCM43 15y ago"Over here at SeatGeek, we were excitedly discussing the tremor when Mike, our trusty sysadmin, realized that our Amazon AWS servers were all in Virginia, right near the epicenter. Did it impact the service at all?"
- rhizome 15y agoI was reflecting on my parent's comment that the actual reasons were opaque due to SG's use of AWS.
- egiva 15y agoYeah, latency is most likely due to the vibrations affecting the various rack components, as commented here. Actually, earthquake-proofing datacenters is a big business in places like the West-Coast USA and Japan: http://www.datacenterknowledge.com/archives/2007/07/17/earthquake-proofing-the-data-center/ http://www.datacenterknowledge.com/archives/2007/07/17/earth...
- pistoriusp 15y agoI remember watching a video about how vibrations can have a negative impact on hard drive latency (Video is at the bottom.): http://blogs.oracle.com/brendan/entry/unusual_disk_latency http://blogs.oracle.com/brendan/entry/unusual_disk_latency