1492 wrote:
sch911 wrote:
Latency is not an issue, period.
May not be for an internet user, but latency is a big concern for businesses. Amazon has said their research indicates they lose $160 million in sales annually for every 100 milliseconds (0.1 sec) of latency. The reason Amazon AWS is so focused on keeping it to a minimum.
That's not quite what the Amazon study said, they said that they could lose $1.6B for every second of additional web page load time. It's hard to find the primary source for this, I've only found
articles that report on it, but none link to the original study. That can't really be extrapolated back to say that they'd lose $160M for 100msec of latency.
But this is irrelevant for the Starlink use case since Starlink is not meant to host business webpages. For the average internet user, latency (within reason) is not that relevant. For me, 50-60msec is fine for interactive use (i.e. connecting to remote servers over SSH or RDP). Online gamers are also latency sensitive and like latencies under 100msec.
But for the average user that's doing streaming or web browsing, even 100msec isn't that noticeable. Traditional satellite latency of 500msec or more is where things start getting noticeable and annoying. I used to maintain servers over a 64kbit Viasat connection and that was an exercise in patience, I could sometimes type entire command lines before I'd see it echoed back.