From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Matt Taggart <matt@lackof.org>
Cc: bloat@lists.bufferbloat.net,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Bloat] [Cerowrt-devel] Ubiquiti Launches a Speed Test Network
Date: Fri, 6 Sep 2019 10:15:33 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1909061010210.21167@uplift.swm.pp.se> (raw)
In-Reply-To: <c2bfb87a-c107-7047-422c-bf31fd6719fd@lackof.org>
On Wed, 4 Sep 2019, Matt Taggart wrote:
> So an interesting idea but they have some things they could improve.
I've been considering what one should run in parallel with the speed test
to get an impression if the speedtest impacts performance of other flows /
realtime flows, similar to what dslreports speedtest does.
I've considered running one or several simulated voip calls (50pps) and
record RTT, PDV, packet loss etc for this session.
It would be interesting to hear any suggestions people have for a fairly
simple codebase that does this that can be included in these kinds of test
clients (both server and client end, and of course one that protects
against reflection attacks etc).
iperf3 can be used for this, but from what I can see the iperf3 server
code isn't very friendly to multiple parallel tests or even resilient
against hung clients that doesn't close the test nicely.
I also considered using WebRTC or VoIP libraries, does anyone know what
RTT/PDV/packet loss data can be extracted from some common ones?
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2019-09-06 8:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 19:49 [Bloat] " Matt Taggart
2019-09-06 8:15 ` Mikael Abrahamsson [this message]
2019-09-06 8:27 ` [Bloat] [Cerowrt-devel] " Toke Høiland-Jørgensen
2019-09-06 9:56 ` Sebastian Moeller
2019-09-06 12:18 ` Mikael Abrahamsson
2019-09-06 17:59 ` Toke Høiland-Jørgensen
2019-09-06 18:33 ` Sebastian Moeller
2019-09-06 22:50 ` Toke Høiland-Jørgensen
2019-09-06 22:56 ` Sebastian Moeller
2019-09-06 23:12 ` Toke Høiland-Jørgensen
2019-09-07 11:33 ` Pete Heist
2019-09-07 12:02 ` Sebastian Moeller
2019-09-07 13:09 ` Pete Heist
2019-09-07 13:47 ` Valdis Klētnieks
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=alpine.DEB.2.20.1909061010210.21167@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=matt@lackof.org \
/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