From: Dave Taht <dave.taht@gmail.com>
To: Arshan Khanifar <arshankhanifar@gmail.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Comparing bufferbloat tests (was: We built a new bufferbloat test and keen for feedback)
Date: Fri, 13 Nov 2020 19:37:57 -0800 [thread overview]
Message-ID: <CAA93jw4YeO2Gh0wvqy3sHjoGnOm5VT7L7Jmfuqk18Z7hkuA4QQ@mail.gmail.com> (raw)
In-Reply-To: <6315456F-AB57-4FDB-9D26-8AA2BB0DF687@gmail.com>
I just wanted to note on this enormous thread that my primary beef
with most speedtests is the too short duration.
cable's "Powerboost" was optimized for speedtests' 20 sec duration.
The internet as a whole ended up optimized for a ~20sec download as a
result.... Run a test for 21 seconds, and boom.
flent defaults to 1minute tests by default and you can clearly see in
many results we've published, the long, slow, miserable, ramp.
A scientific way of compensating for the balance of user attention and
an accurate test would be to always run some
subset of the tests initiated by users for this longer duration and
cross check those results.
next prev parent reply other threads:[~2020-11-14 3:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 21:30 [Bloat] We built a new bufferbloat test and keen for feedback Sam Westwood
2020-11-04 23:43 ` Michael Richardson
2020-11-04 23:54 ` Toke Høiland-Jørgensen
2020-11-05 1:52 ` Y
2020-11-05 0:23 ` Dave Collier-Brown
2020-11-05 11:48 ` Toke Høiland-Jørgensen
2020-11-05 13:24 ` [Bloat] Comparing bufferbloat tests (was: We built a new bufferbloat test and keen for feedback) Dave Collier-Brown
2020-11-05 14:24 ` Toke Høiland-Jørgensen
2020-11-05 16:06 ` Arshan Khanifar
2020-11-05 17:25 ` Toke Høiland-Jørgensen
2020-11-06 16:03 ` Stephen Hemminger
2020-11-06 16:17 ` Toke Høiland-Jørgensen
2020-11-06 17:05 ` Sebastian Moeller
2020-11-08 22:07 ` Arshan Khanifar
2020-11-14 3:37 ` Dave Taht [this message]
2020-11-14 23:14 ` Michael Richardson
2020-11-05 8:21 ` [Bloat] We built a new bufferbloat test and keen for feedback Sebastian Moeller
2020-11-05 21:30 ` Sam
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=CAA93jw4YeO2Gh0wvqy3sHjoGnOm5VT7L7Jmfuqk18Z7hkuA4QQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=arshankhanifar@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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