![]() aaaand remember that it's persistent (for just the tab) until you turn it back off :) lol)Įdit: Just found downthread describing seeing 100Mbps through a 10Mbit hub. Now I'm curious what model PHY (well, NIC) you're using.įWIW, Chrome's devtools has a network rate limiter built in (network tab, dropdown that says "No throttling", open that and hit "add". I think speedtest websites try to measure both the burst rate and the line rate, so perhaps something's gotten very tangled up on both the PHY and JS sides. Remembering that experience got me thinking - without any idea what I'm talking about, I'm wondering if the PHY layer is doing something vaguely similarly stupid-simple that does technically limit the line rate to 10Mb at full blast, but still allows throughput to very briefly burst higher than that. (I'm still looking for a way to synthetically limit a link in ways that are physically accurate.) IIRC I was just playing with the default approaches you'd find bandied about on tutorial websites and such. ![]() ![]() While stumbling around attempting to figure out `tc qdisc` a while back I found that the shaping it was applying was very synthetic, such that asking for low bitrate and high latency would mean the kernel would just wait a second or two then shunt several KB of data through at once. You mean you told the PHY to renegotiate at 10M with something like `ethtool -s speed 10`? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |