Why I quit this battle
badmodems.com
Why I quit this battle
1–10 of 126 posts
Re: Why I quit this battle
#2Re: Why I quit this battle
#3Re: Why I quit this battle
#4Thanks for all the fish!
Re: Why I quit this battle
#5Re: Why I quit this battle
#6> Some chip makers have hidden latency and jitter issues from common tests that are in use by consumers and even ISPs. Ping CANNOT be used reliably to test for latency or jitter.
Re: Why I quit this battle
#7Who is this Kevin from DSLReport?
He seems to know what he's talking about, but is also invested enough to become a potential sell out.
Re: Why I quit this battle
#8Re: Why I quit this battle
#9The site seems to be focusing on latency/jitter issues: https://web.archive.org/web/20210506114456fw_/https://badmod...
I'm not entirely sure what to make of the information presented. The page above includes an embedded video demonstrating a difference between ICMP and TCP load-testing: https://www.youtube.com/watch?v=15cJ400yR_E
I'm not knocking that there is interesting data, I'm rather trying to consider potential confounding factors that could call the conclusions being drawn into question.
In particular, I have two questions:
- This doesn't talk about "bufferbloat" (https://en.wikipedia.org/wiki/Bufferbloat) or internal buffering happening inside the modem, only latency/jitter. I'm honestly completely naive about the relationship between the two concepts, but I thought they had reasonable overlap, and could even potentially go some way to explaining the dynamics of what's going on. Why not?
- The video seems to just be TCP- and ICMP-pinging 8.8.8.8. Surely that address is sufficiently hammered that it probably implements fairly aggressive rate control algorithms...?
Re: Why I quit this battle
#10Who is this Kevin from DSLReport?
Semi-famous camera guy, read a few of his camera reviews. He seems to know what he's talking about, but is also invested enough to become a potential sell out.
But the entire thread was hard to follow on that site. There wasn’t much context.