Flent-users discussion archives
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <notifications@github.com>
To: tohojo/flent <flent@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: Re: [Flent-users] [tohojo/flent] Charting ping_hosts (#181)
Date: Wed, 11 Sep 2019 10:27:38 -0700	[thread overview]
Message-ID: <tohojo/flent/issues/181/530481882@github.com> (raw)
In-Reply-To: <tohojo/flent/issues/181@github.com>


[-- Attachment #1.1: Type: text/plain, Size: 1475 bytes --]

Rich Brown <notifications@github.com> writes:

> Actually, I want the ability to plot the "best"`ping_host` (that is, lowest latency host), since that's going to display the biggest variance. A few milliseconds of additional bloat added to the 90msec from my house to Fremont is easy to ignore. Tacking a few milliseconds onto 16msec from Cloudflare's DNS shows a significant delta - and worth reporting.
>
> For example, here are ping times for various hosts from my house and (in paren's from netperf.bufferbloat.net in Atlanta):
>
> * flent-fremont.bufferbloat.net ~90msec (~53msec)
> * netperf.bufferbloat.net ~40msec (~30 microseconds - Duh :-)
> * gstatic.com and 8.8.8.8 (Google's all-purpose host and DNS) is ~21-22msec (~15msec)
> * Cloudflare's 1.1.1.1 (anycast address, I suspect) is ~16msec (< 300 microseconds)
>
> So my preference would be to have a way to tell Flent to use ping
> times from another host besides the -H host.

Hmm, that is not easily doable as it is now, unfortunately...

One way to achieve something like it is to add another test parameter
that would override the ping destination of the existing tests. I.e.,
instead of adding a new ping host, you'd just get the ability to
override the one(s) already defined by the test...

Would that work for you?


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/181#issuecomment-530481882

[-- Attachment #1.2: Type: text/html, Size: 2996 bytes --]

[-- Attachment #2: Type: text/plain, Size: 151 bytes --]

_______________________________________________
Flent-users mailing list
Flent-users@flent.org
http://flent.org/mailman/listinfo/flent-users_flent.org

  parent reply	other threads:[~2019-09-11 17:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-10 15:39 Rich Brown
2019-09-11 11:54 ` Rich Brown
2019-09-11 12:05 ` Rich Brown
2019-09-11 12:07 ` Toke Høiland-Jørgensen
2019-09-11 12:17 ` Rich Brown
2019-09-11 15:15 ` Toke Høiland-Jørgensen
2019-09-11 16:12 ` Rich Brown
2019-09-11 17:27 ` Toke Høiland-Jørgensen [this message]
2019-09-11 18:13 ` Rich Brown
2019-09-13 16:27 ` Toke Høiland-Jørgensen
2019-09-13 17:13 ` Rich Brown
2019-09-13 22:01 ` Toke Høiland-Jørgensen
2019-09-14  1:45 ` 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.flent.org/postorius/lists/flent-users.flent.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=tohojo/flent/issues/181/530481882@github.com \
    --to=notifications@github.com \
    --cc=flent@noreply.github.com \
    --cc=reply+AHVNJP5G6FF2Z46TPWBPEA53QZQQVEVBNHHB2T4L5Y@reply.github.com \
    --cc=subscribed@noreply.github.com \
    --subject='Re: [Flent-users] [tohojo/flent] Charting ping_hosts (#181)' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox