General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Sina Khanifar <sina@waveform.com>, bloat <bloat@lists.bufferbloat.net>
Cc: sam@waveform.com
Subject: Re: [Bloat] Updated Bufferbloat Test
Date: Thu, 25 Feb 2021 15:48:01 +0100	[thread overview]
Message-ID: <87ft1k19we.fsf@toke.dk> (raw)
In-Reply-To: <87r1l41gel.fsf@toke.dk>

Toke Høiland-Jørgensen <toke@toke.dk> writes:

>>   * We tried really hard to get as close to saturating gigabit
>> connections as possible. We redesigned completely the way we chunk
>> files, added a “warming up” period, and spent quite a bit optimizing
>> our code to minimize CPU usage, as we found that was often the
>> limiting factor to our speed test results.
>
> Yup, this seems to work better now! I can basically saturate my
> connection now; Chromium seems to be a bit better than Firefox in this
> respect, but I ended up getting very close on both:
>
> Chromium:
> https://www.waveform.com/tools/bufferbloat?test-id=b14731d3-46d7-49ba-8cc7-3641b495e6c7
> Firefox:
> https://www.waveform.com/tools/bufferbloat?test-id=877f496a-457a-4cc2-8f4c-91e23065c59e
>
> (this is with a ~100Mbps base load on a Gbps connection, so at least the
> Chromium result is pretty much link speed).

Did another test while replacing the queue on my router with a big FIFO.
Still got an A+ score:

https://www.waveform.com/tools/bufferbloat?test-id=9965c8db-367c-45f1-927c-a94eb8da0e08

However, note the max latency in download; quite a few outliers, jet I
still get a jitter score of only 22.6ms. Also, this time there's a
warning triangle on the "low latency gaming" row of the table, but the
score is still A+. Should it really be possible to get the highest score
while one of the rows has a warning in it?

-Toke

      reply	other threads:[~2021-02-25 14:48 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24 18:22 Sina Khanifar
2021-02-24 22:10 ` Dave Taht
2021-02-24 23:39   ` Simon Barber
2021-02-25  5:56   ` Sina Khanifar
2021-02-25  7:15     ` Simon Barber
2021-02-25  7:32       ` Sina Khanifar
2021-02-25 13:38         ` Simon Barber
2021-02-25 13:43           ` Dave Taht
2021-02-25 13:49           ` Mikael Abrahamsson
2021-02-25 13:53             ` Simon Barber
2021-02-25 19:47               ` Sina Khanifar
2021-02-25 19:56                 ` Simon Barber
2021-02-25 20:10                   ` Sina Khanifar
2021-02-25 20:52                     ` Simon Barber
2021-02-25 20:53                     ` Simon Barber
2021-02-25 13:46         ` Simon Barber
2021-02-25  7:20     ` Simon Barber
2021-02-25 10:51     ` Sebastian Moeller
2021-02-25 20:01       ` Sina Khanifar
2021-02-25 20:14         ` Sebastian Moeller
2021-02-26  1:06           ` Daniel Lakeland
2021-02-26  8:20             ` Sina Khanifar
2021-02-26 17:25               ` Michael Richardson
2021-02-24 22:15 ` Kenneth Porter
2021-02-25  5:29   ` Kenneth Porter
2021-02-25  5:35     ` Dave Taht
2021-02-25  6:24       ` Kenneth Porter
2021-02-25  1:16 ` David Collier-Brown
2021-02-25  6:21   ` Sina Khanifar
2021-02-25  4:48 ` Marco Belmonte
     [not found] ` <1D68EF40C3A8A269831408C8@172.27.17.193>
2021-02-25  5:58   ` Sina Khanifar
2021-02-25  9:47 ` Mikael Abrahamsson
2021-02-25 10:49 ` Sebastian Moeller
2021-02-25 20:41   ` Sina Khanifar
2021-02-25 20:50     ` Sina Khanifar
2021-02-25 21:15       ` Sebastian Moeller
2021-02-26  8:23         ` Sina Khanifar
2021-02-26 18:41           ` Sina Khanifar
2021-02-26 19:58             ` Sebastian Moeller
2021-02-25 12:27 ` Toke Høiland-Jørgensen
2021-02-25 14:48   ` Toke Høiland-Jørgensen [this message]

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=87ft1k19we.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=bloat@lists.bufferbloat.net \
    --cc=sam@waveform.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