3 ms·

Ah, apologies for not responding here. It's (shocks in disgust) a Realtek one, I forgot which specifically, but the "smart" switch (ugh, I hate the naming every

Ah, apologies for not responding here. It's (shocks in disgust) a Realtek one, I forgot which specifically, but the "smart" switch (ugh, I hate the naming everything smart) definitely said that it's only a 10M Ethernet connection. Using Chrome's limiter, capped at 5,000,000 bits/sec (5Mbps) both direction: Speedtest.net: 5.00Mbps in both directions (nice, are they're including overhead in these calculations?) Cloudflare: 4.80Mbps downlink, 4.81Mbps uplink (well, it's true now) Fast.com: 5.0Mbps downlink, 58Mbps uplink (holy crap, that's not what I've expected) So I will re-test Cloudflare again at link-limited PHY, but Fast.com's test seems a little weird.

exikyut 5y ago
All good - realtek aren't that bad at the end of the day, I'm running my internet connection through a 100M ADMtek card from ~2004 :D Well it probably was 10M then. The port LED on the switch might've changed color as well. (Smart reminds me of the consumer-lite answer to SDN.) I just tried fast.com myself using 100kbps and it quite happily measured at line rate (6.8M+800k, yay D:). For some bizarre reason I found I needed to open a new tab, open the devtools, set the network speed, then load fast.com for it to work. My guess is that Chrome applies connection ratelimiting metadata as new connections are created, such that existing sockets still in keepalive aren't affected. I'd say that's at least a documentation bug. I'm not really able/sure how to reproduce the other comment I linked (using an actual 10M switch and seeing 100M of throughput). That's really interesting.