General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Sina Khanifar <sina@waveform.com>
Cc: bloat <bloat@lists.bufferbloat.net>, "Dave Täht" <dave.taht@gmail.com>
Subject: Re: [Bloat] waveform bufferbloat test is GOOOD
Date: Wed, 3 Feb 2021 22:03:48 +0100	[thread overview]
Message-ID: <9DA93F1C-8988-4CF9-A8BE-2DFA4ED85E67@gmx.de> (raw)
In-Reply-To: <CABF4YOUDWDQ1sgbULaTBMyEfUz1V14_sd3XEeKYL_VU1oC1V6A@mail.gmail.com>

@Dave,


using Chrome instead of Safari I get this with SQM:
https://www.waveform.com/tools/bufferbloat?test-id=ee977631-2f50-4105-b717-5066cbf3ddca
Unloaded: 		15 ms
Download Active:	+0 ms
Upload Active:		+0 m

this with SQM disabled:
https://www.waveform.com/tools/bufferbloat?test-id=0959dcfa-04e2-435c-9924-0d0438420597
Unloaded: 		15 ms
Download Active:	+14 ms
Upload Active:		+50 m

and this with SQM enabled again:
https://www.waveform.com/tools/bufferbloat?test-id=154ee895-108e-4bcf-8a08-536340fb5282
Unloaded: 		15 ms
Download Active:	+1 ms
Upload Active:		+0 m

all measured via an USB3 realtek gigabit-ethernet dongle on a macbook with 10.14.6.

To me this looks like cake really helps, but I wonder what TCP is in use by cloudflare's CDN nodes... I had expected somewhat larger effects.

Best Regards
	Sebastian


> On Feb 3, 2021, at 12:54, Sina Khanifar <sina@waveform.com> wrote:
> 
> Hi all,
> 
> It's funny that this thread should pop up now … I  drafted a long
> email to send to the list two nights ago. I was planning to announce
> that we were almost ready to actually launch our updated bufferbloat
> test, but then we found some pesky bugs that we're now working to
> squash.
> 
> We should have them all sorted out this week or early next week, and
> I'll finally send my longer email to the group that covers all the
> changes we made since we shared an early beta a couple of months back.
> 
> Best,
> 
> Sina.
> 
> On Wed, Feb 3, 2021 at 1:42 AM Sebastian Moeller <moeller0@gmx.de> wrote:
>> 
>> Hi Dave,
>> 
>> 
>> I wonder what is going on with the reported latencies. I see negative latency numbers indicating that the report is presenting a difference, maybe unloaded minus the direction under tests? My tests with SQM also report the unloaded latency figure ion the top right as 0ms (while my link forces A >=12ms RTT to the first IP address after my router). I would guess that there is still some development going on and hopefully that will be fixed.
>> 
>> Best Regards
>>        Sebastian
>> 
>> 
>> 
>> 
>>> On Feb 2, 2021, at 17:27, Dave Taht <dave.taht@gmail.com> wrote:
>>> 
>>> Regrettably my joy only lasted a few hours, as there was confirmation
>>> bias. Try it with sqm off or on. Running a complete battery of tests
>>> now.
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On Tue, Feb 2, 2021 at 5:55 AM Jonathan Foulkes <jf@jonathanfoulkes.com> wrote:
>>>> 
>>>> Excellent, nice to see another comprehensive test.
>>>> I also like that they list the IQrouter in the set of routers that mitigate bloat ;-)
>>>> 
>>>> Since I recently shared the DSLreports test from my line, here is the same line tested via this new site:
>>>> https://www.waveform.com/tools/bufferbloat?test-id=f10cfe50-6dd2-4ae3-9b40-dedd2b5087c6
>>>> 
>>>> Nice to see that A+ and zeros for bloat.
>>>> 
>>>> for reference, the dslreports test: https://www.dslreports.com/speedtest/67140120
>>>> 
>>>> Cheers,
>>>> 
>>>> Jonathan
>>>> 
>>>> On Feb 1, 2021, at 10:33 PM, Dave Taht <dave.taht@gmail.com> wrote:
>>>> 
>>>> https://www.waveform.com/tools/bufferbloat?test-id=bea9f548-086a-4a74-bbde-b05b33f689a2
>>>> 
>>>> I am very happy with this test, and I must admit, if it was discussed
>>>> here, already, I must have missed the thread. Not only is the test
>>>> well structured and fast - and some people like whisker plots more
>>>> than me, my blessed cdfs, & the FAQ is brilliant.
>>>> 
>>>> https://www.waveform.com/tools/bufferbloat#erid5407983
>>>> 
>>>> 
>>>> --
>>>> "For a successful technology, reality must take precedence over public
>>>> relations, for Mother Nature cannot be fooled" - Richard Feynman
>>>> 
>>>> dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729
>>>> _______________________________________________
>>>> Bloat mailing list
>>>> Bloat@lists.bufferbloat.net
>>>> https://lists.bufferbloat.net/listinfo/bloat
>>>> 
>>>> 
>>> 
>>> 
>>> --
>>> "For a successful technology, reality must take precedence over public
>>> relations, for Mother Nature cannot be fooled" - Richard Feynman
>>> 
>>> dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729
>>> _______________________________________________
>>> Bloat mailing list
>>> Bloat@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/bloat
>> 
>> _______________________________________________
>> Bloat mailing list
>> Bloat@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bloat


  reply	other threads:[~2021-02-03 21:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-02  3:33 Dave Taht
2021-02-02 13:55 ` Jonathan Foulkes
2021-02-02 16:27   ` Dave Taht
2021-02-03  9:42     ` Sebastian Moeller
2021-02-03 11:54       ` Sina Khanifar
2021-02-03 21:03         ` Sebastian Moeller [this message]
2021-02-04  9:43         ` Michael Yartys

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9DA93F1C-8988-4CF9-A8BE-2DFA4ED85E67@gmx.de \
    --to=moeller0@gmx.de \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=sina@waveform.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox