3 ms·
> Yet each request still has a 100-200ms latency or more, which becomes noticeable in user interactions ping dawn-night-7975.fly.dev --- dawn-night-797
by dustingetz 2y ago
> Yet each request still has a 100-200ms latency or more, which becomes noticeable in user interactions
ping dawn-night-7975.fly.dev
--- dawn-night-7975.fly.dev ping statistics ---
6 packets transmitted, 6 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 11.566/12.635/14.000/0.841 ms
so, 6ms each way from my house in the suburbs of Philadelphia, to the closest Fly region near NYC about 80 miles away. When measuring UI response latency, this is the number that matters. No, your database is not in the edge. But cached query results are!
- nchmy 2y agonot everyone lives 6ms away from a fly.io (or even cloudflare) datacenter. And, moreover, everyone suffers from lapses in internet connectivity
- dustingetz 2y ago1) yes but everyone does NOT live “100-200” ms away, so i think we’d all appreciate if the local first vendor went and measured the real number rather than pulling this completely fake 100-200 ms number out of their ass (justified in the image with a big blue line across the Atlantic from Germany to SF, no less!). invoking the “Call of Duty” test - if you can play online shooter games, then you can get a sub-40ms ping to a game server in your region 2) engineering is done with numbers. Which market of “everyone”? Half the world is enterprise workbench software, and when slack goes down all work stops. We aren’t trying to make customer support software work in the subway. What exact market are we targeting that does?