Yes, it looks like typical head-of-line blocking with a multi-second
buffer. To smooth it out, you would need an averaging window wider than
the effective (bloated) RTT.
A tell-tale symptom is that the width of the gap, in which little or no
progress is made at the application layer, is
Is this classic buffer bloat on 50 megabit cable modem?
https://www.dslreports.com/forum/r31035315-Weird-speed-test-results-It-falls-off-right-at-the-end
by extending the download duration to 30 seconds, what looks like
a speed "fall-off at the end" reveals two complete stall/recoveries, and
> On 13 Oct, 2016, at 06:22, Dave Taht wrote:
>
> I still might quibble, but a trimmed mean makes more sense than just a mean.
>
> Problem I always have is bloat is biased always towards the end of a test.
> Here,
> at 1gbit, it took nearly 20 seconds to start going boom.
It is done
under the trimmed mean method, that would be a "C" grade result.
On Thu, Oct 13, 2016 at 11:46 AM, jb wrote:
> Actually I think the concept I need is the trimmed mean.
> throwing away the highest couple of values (lowest couple are not to be
> thrown away because
This has major bloat happening at the end of the upload test. Which
worries me - here, at a gbit.
http://www.dslreports.com/speedtest/5284047
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
___