From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Getting bloat tests into open source speedtest
Date: Tue, 03 Sep 2019 15:05:55 +0200 [thread overview]
Message-ID: <87ftlda5sc.fsf@toke.dk> (raw)
In-Reply-To: <alpine.DEB.2.20.1909031404500.21548@uplift.swm.pp.se>
Mikael Abrahamsson <swmike@swm.pp.se> writes:
> On Tue, 3 Sep 2019, Toke Høiland-Jørgensen wrote:
>
>> Hi everyone
>>
>> I came across this open source speedtest: https://www.netztest.at/en/
>> (also run by nic.cz and integrated into the Turris Omnia firmware:
>> https://www.netmetr.cz/en/ ).
>>
>> Only issue is that it doesn't test for bufferbloat. So, I opened an
>> issue on the upstream repo; this is the link, in case anyone else wants
>> to participate in the discussion:
>> https://github.com/rtr-nettest/open-rmbt/issues/6
>
> This is the swedish local speedtest run by .SE:
>
> https://github.com/dotse/bbk
Hmm, I think my old university actually had a project to add it at some
point. Not sure what happened to that...
> I've asked them for bufferbloat tests as well, so... if anyone want to do
> anything, that'd be nice.
>
> What codebase does dslreports speedtest use, it seems to have a very nice
> bufferbloat test?
I think it's proprietary, but I'm not sure...
-Toke
next prev parent reply other threads:[~2019-09-03 13:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 11:39 Toke Høiland-Jørgensen
2019-09-03 11:41 ` Sebastian Moeller
2019-09-03 11:45 ` Toke Høiland-Jørgensen
2019-09-03 12:01 ` Sebastian Moeller
2019-09-03 12:05 ` Mikael Abrahamsson
2019-09-03 13:05 ` Toke Høiland-Jørgensen [this message]
2019-09-04 19:48 ` Kenneth Porter
[not found] <mailman.587.1567520500.1240.bloat@lists.bufferbloat.net>
2019-09-03 15:21 ` Rich Brown
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=87ftlda5sc.fsf@toke.dk \
--to=toke@toke.dk \
--cc=bloat@lists.bufferbloat.net \
--cc=swmike@swm.pp.se \
/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