From: Dave Taht <dave.taht@gmail.com>
To: "Carlos R. Pasqualini" <pasqualinic@fcal.uner.edu.ar>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Self-hosted speed test
Date: Thu, 7 Dec 2017 11:17:31 -0800 [thread overview]
Message-ID: <CAA93jw5YDOF=S-xqkVmFH3VA_2xo5QS-9POygKh8evOOZcx22g@mail.gmail.com> (raw)
In-Reply-To: <1512673617.2361.50.camel@fcal.uner.edu.ar>
All the servers need for basic flent testing is netperf (netserver).
Other tools like irtt are helpful.
The problem with flent's toolset in comparison with your suggestion is
that having a browser based test is useful.
However, we have generally found browser based tests to be
increasingly inaccurate at speeds > 40Mbit.
prev parent reply other threads:[~2017-12-07 19:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 19:06 Carlos R. Pasqualini
[not found] ` <CAJq5cE3dyKqoRxc4PYvijjj+VwNJhPt8o+cf1hG-kNdWOiTK5g@mail.gmail.com>
[not found] ` <CAJq5cE2ekh3aVAKs47fgEY=QebUyVN7FGynMxMSbGZb81Wv7kg@mail.gmail.com>
2017-12-07 19:10 ` Jonathan Morton
2017-12-07 19:24 ` Carlos R. Pasqualini
2017-12-07 19:17 ` Dave Taht [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='CAA93jw5YDOF=S-xqkVmFH3VA_2xo5QS-9POygKh8evOOZcx22g@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=pasqualinic@fcal.uner.edu.ar \
/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