From: Sebastian Moeller <moeller0@gmx.de>
To: Sina Khanifar <sina@waveform.com>
Cc: "Dave Täht" <dave.taht@gmail.com>,
sam@waveform.com, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Updated Bufferbloat Test
Date: Thu, 25 Feb 2021 11:51:33 +0100 [thread overview]
Message-ID: <5CB9F40C-5FFB-4ABC-A184-A3C3A29D2413@gmx.de> (raw)
In-Reply-To: <CABF4YOVn0MuxVKR07SB6HHZc3N=gP9rMqp_vdxtCGCh6Z6Z_Nw@mail.gmail.com>
Hi Sina,
> On Feb 25, 2021, at 06:56, Sina Khanifar <sina@waveform.com> wrote:
>
> Thanks for the feedback, Dave!
>
>> 0) "average" jitter is a meaningless number. In the case of a videoconferencing application, what matters most is max jitter, where the app will choose to ride the top edge of that, rather than follow it. I'd prefer using a 98% number, rather than 75% number, to weight where the typical delay in a videoconfernce might end up.
>
> Both DSLReports and Ookla's desktop app report jitter as an average
> rather than as a max number, so I'm a little hesitant to go against
> the norm - users might find it a bit surprising to see much larger
> jitter numbers reported. We're also not taking a whole ton of latency
> tests in each phase, so the 98% will often end up being the max
> number.
> [...]
[SM] Maybe the solution would be to increase the frequency of the RTT measures and increase the quantile somewhat, maybe 90 or 95?
Best Regards
Sebastian
next prev parent reply other threads:[~2021-02-25 10:51 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 [this message]
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
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=5CB9F40C-5FFB-4ABC-A184-A3C3A29D2413@gmx.de \
--to=moeller0@gmx.de \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--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