Hi folks, A couple comments re: the DSLReports Speed Test.
1) It's just becoming daylight for Justin, so he hasn't had a chance to respond to all these notes. :-) 2) In a private note earlier this week, he mentioned that he uses "websocket pings" which he believes are pretty speedy/low latency. 3) He does have plans to incorporate stats from the server end's TCP stack (cwnd, packet loss, retransmissions, etc.) in a future version of the speed test. I imagine it would help him to know what you'd like to see... Best, Rich On Apr 19, 2015, at 1:15 PM, Mikael Abrahamsson <[email protected]> wrote: > On Sun, 19 Apr 2015, Toke Høiland-Jørgensen wrote: > >> The upload latency figures are definitely iffy, but the download ones seem >> to match roughly what I've measured myself on this link. > > Also, I don't trust parallel latency measures done by for instance ICMP ping. > Yes, they indicate something, but what? > > We need insight into the TCP stack. So how can an application like > dslresports that runs in a browser, get meaningful performance metrics on its > measurement TCP-sessions from the OS TCP stack? This is a multi-layer problem > and I don't see any meaningful progress in this area... > > -- > Mikael Abrahamsson email: > [email protected]_______________________________________________ > Bloat mailing list > [email protected] > https://lists.bufferbloat.net/listinfo/bloat _______________________________________________ Bloat mailing list [email protected] https://lists.bufferbloat.net/listinfo/bloat
