[Starlink] [Rpm] so great to see ISPs that care

[Ben Greear]

On 3/12/23 2:02 PM, rjmcmahon via Starlink wrote:
> iperf 2 uses responses per second and also provides the bounce back times as well as one way delays.
> 
> The hypothesis is that network engineers have to fix KPI issues, including latency, ahead of shipping products.
> 
> Asking companies to act on consumer complaints is way too late. It's also extremely costly. Those running Amazon customer service can explain how these consumer 
> calls about their devices cause things like device returns (as that's all the call support can provide.) This wastes energy to physically ship things back, 
> causes a stack of working items that now go to ewaste, etc.
> 
> It's really on network operators, suppliers and device mfgs to get ahead of this years before consumers get their stuff.
> 
> As a side note, many devices select their WiFi chanspec (AP channel+) based on the strongest RSSI. The network paths should be based on KPIs like low latency. 
> Strong signal just means an AP is yelling to loudly and interfering with the neighbors. Try the optimal AP chanspec that has 10dB separation per spatial 
> dimension and the whole apartment complex would be better for it.

How are you going to make the latency determination?

I guess that anywhere there are a lot of APs you can connect to, they are managed
entity with some sort of global controller for that location.  So then the controller can make
the decision.  That general ability for controller to manage stations already
exists in wifi, but someone will have to make a clever controller...

If it is wired/fiber backhaul, then probably everyone shares same uplink so selecting strongest
AP is best option.

If wifi backhaul, you need a lot more cleverness to manage stations properly.

Thanks,
Ben

-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com