AWS data center latencies, visualized
91–100 of 223 posts
Re: AWS data center latencies, visualized
#92Earlier quoted context omitted.
Do you have some kind of an accessibility tool for this? Maybe a whole screen filter that changes colors in a specific way so you can distinguish them?
No I don't. It's actually not a big deal in day-to-day life. People often go "But how the hell can you drive if you can't distinguish red from green at the stoplight?"... in reality it's more nuanced. As another comment already mentioned, perception varies across even among colorblind people. I find it hard to distinguish R/G if the colors are not fully saturated or in low-light situation. Also the brain knows that "…
But I was curious if one needs to rely on the application developers to deliver a solution or if there was a generalized filter or whatever that would work always. Maybe like screen readers, those work fine if the app does not do something horrible. But with some help from apps, they perform much better.
Re: AWS data center latencies, visualized
#93Us-east-1 is hard to beat. Close to the network centrality of the of the internet, low latency to both the west coast and Europe.
Re: AWS data center latencies, visualized
#94Just curious, why is there no us central or us texas region? It could maybe be useful.
I think a lot of people are sleeping on the benefits of hosting workloads in these regions. Many finance, banking & insurance companies have already taken advantage. Most of your credit card transactions are handled by data centers that live ~barycentric to the continental US. Much of small US banking tech happens in places like Missouri.
Re: AWS data center latencies, visualized
#95I have red-green color blindness, which makes it hard/impossible for me to distinguish between the 200ms lines. This affects about 8% of male population btw, maybe you can add a color-blind mode, very nice visualization otherwise!
Maybe we should be less critical specially with "Make it fit for my workflow" type comment, and more so if it is built by some random guy in their free time, and not say a project which is asking money.
Re: AWS data center latencies, visualized
#96I have red-green color blindness, which makes it hard/impossible for me to distinguish between the 200ms lines. This affects about 8% of male population btw, maybe you can add a color-blind mode, very nice visualization otherwise!
It's sad that this is the top comment for the post. Many people have stopped posting their crappy work online due to harsh comments like yours. There's no easy reply to your comment. Maybe we should be less critical specially with "Make it fit for my workflow" type comment, and more so if it is built by some random guy in their free time, and not say a project which is asking money.
Re: AWS data center latencies, visualized
#97I have red-green color blindness, which makes it hard/impossible for me to distinguish between the 200ms lines. This affects about 8% of male population btw, maybe you can add a color-blind mode, very nice visualization otherwise!
It's sad that this is the top comment for the post. Many people have stopped posting their crappy work online due to harsh comments like yours. There's no easy reply to your comment. Maybe we should be less critical specially with "Make it fit for my workflow" type comment, and more so if it is built by some random guy in their free time, and not say a project which is asking money.
Re: AWS data center latencies, visualized
#98Anyways, although this looks cool, it'd be much more easily understandable in a 2d map instead of a rotating one.
Re: AWS data center latencies, visualized
#99Earlier quoted context omitted.
As a quick workaround, you can set a CSS filter on the whole page: Either use dev tools to put a rule `filter: hue-rotate(60deg);` on the `body` element, or simply run `javascript:void(document.body.style.filter='hue-rotate(60deg)')` from the url bar.
Nice hack, thank you! :-)
Re: AWS data center latencies, visualized
#100Earlier quoted context omitted.
Oh shit! Thanks. Good point. That actually makes it more plausible, as K is smaller.
1/2 c in circuit boards (FR-4), 1/3 c in cables, two useful numbers to remember.
1/2 c ~ 150 km/ms in circuit board.
1/3 c ~ 100 km/ms in cable. And...
2/3 c ~ 200 km/ms in fiber?
I'm a bit confused about difference between cable and fiber heh :)