4 ms·
I was trying to figure out how this guy could be so behind the times - just discovered internal network latency at AWS? Then I saw: Published: 9:01 AM GMT, T
by trotsky 13y ago
I was trying to figure out how this guy could be so behind the times - just discovered internal network latency at AWS?
Then I saw:
Published:
9:01 AM GMT, Tuesday, 12 January 2010
- ultimoo 13y agoYes, the year of the blog should definitely be present in the HN title. That said, what is the deal with the internal network latency and the other points the OP touched upon today? Did Amazon get around to resolving things, or have things worsened?
- seldo 13y agoMy non-rigorous impression is that latency is roughly the same now as it was in 2010, i.e. not great, but at least it hasn't been getting worse.
- t0 13y agoCan you enlighten us? Why is it so slow? Are some people abusing all of that free bandwidth? Is their LAN simply not built to handle much traffic?
- trotsky 13y agoI don't have any inside information, but I would guess it's because their san is so sketchy everyone rolls their own DFS and uses other chatty replication strategies, leaving the network running data and disk on the same topology. These days a lot of that traffic will take 4 hops within an AZ.
- redact207 13y agoHave there been any improvements since then?
- codewright 13y agoNo, it's still common to have in-house "find a good node" code that fires up and takes down machines until one that will be reliable is found.
- wmf 13y agoPrevious HN discussion: https://news.ycombinator.com/item?id=1048694 https://news.ycombinator.com/item?id=1048694