From: Sebastian Moeller <moeller0@gmx.de>
To: Sergio Belkin <sebelk@gmail.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Is still netperf a valid tool?
Date: Sun, 14 Jun 2020 16:55:34 +0200 [thread overview]
Message-ID: <AD6293EA-AB2F-421D-92BE-BCA7F21D348A@gmx.de> (raw)
In-Reply-To: <CABZC=5zUvH0PZEoga2iWydJkVXOKMZCytQGuYV134aG3w9waPQ@mail.gmail.com>
Hi Sergio,
IMHO netperf is a convenient toll to generate load, and for measuring bufferbloat, or latency under load increase, generating saturating loads is an important step. So I see no reason why the fct that netperf is relatively mature and sees only little change nowadays speaks against using it. I note that optionally the actual latency measurement can/will be performed using irtt...
I guess the real experts will be able to offer a more nuanced opinion...
Best Regards
Sebastian
> On Jun 14, 2020, at 16:36, Sergio Belkin <sebelk@gmail.com> wrote:
>
> Hi,
> I've seen that many of the recommended tools to diagnose/troubleshoot bufferbloat use netperf.
> Netperf in https://github.com/HewlettPackard/netperf has many years of inactivity. In fact, in recent versions of distros don't include it.
> So, my question is: is still netperf a reliable tool?
> Thanks in advance!
> --
> --
> Sergio Belkin
> LPIC-2 Certified - http://www.lpi.org
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2020-06-14 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 14:36 Sergio Belkin
2020-06-14 14:55 ` Sebastian Moeller [this message]
2020-06-15 9:15 ` Toke Høiland-Jørgensen
2020-06-16 1:22 ` Sergio Belkin
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=AD6293EA-AB2F-421D-92BE-BCA7F21D348A@gmx.de \
--to=moeller0@gmx.de \
--cc=bloat@lists.bufferbloat.net \
--cc=sebelk@gmail.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