From: "Toke Høiland-Jørgensen" <notifications@github.com> To: tohojo/flent <flent@noreply.github.com> Cc: Comment <comment@noreply.github.com>, flent-users <flent-users@flent.org> Subject: Re: [Flent-users] [tohojo/flent] packet loss stats (#106) Date: Thu, 16 Nov 2017 12:15:45 +0000 (UTC) [thread overview] Message-ID: <tohojo/flent/issues/106/344905911@github.com> (raw) In-Reply-To: <tohojo/flent/issues/106@github.com> [-- Attachment #1.1: Type: text/plain, Size: 2983 bytes --] Pete Heist <notifications@github.com> writes: > Cool, the rrul_be_irtt test is working for me. I see what you mean, > ideally it would just be the same test but you substitute the tool you > want to use for a particular measurement. > > Maybe this is what you're saying, but could it be that you specify > what tool you want to use for each particular measurement? In other > words, the tool for 'TCP throughput' is netperf as of now, and later > could possibly be iperf. For 'UDP RTT' it can be netperf or irtt. For > 'ICMP RTT' it can be ping or fping, etc. Yeah, something like that. For ping we already do this (default to fping and fall back to regular ping), but those are closer in functionality. But the idea is the same; the test should not specify "use netperf" but rather "this is a UDP RR test". Then we pick irtt if it's available and use netperf as a fallback. Optionally with a command line switch to force fallback (probably a good idea at least until we get wider deployment of irtt). > I'm waving my arms here because there can be more than one measurement > from a single tool. So maybe it should really be 'UDP RT' because in > the case of irtt it's doing a UDP round-trip and measuring several > things from it at once: RTT, OWD, IPDV, etc. Since there isn't a > one-to-one correspondence between the tool and measurement it returns, > it's not clear to me yet how it should be specified, still thinking > about it. > > I guess at some point there will be additional plots for OWD and IPDV. > Is it a new situation for you that the plots available depend not only > on the test but the tool used or even its settings? Meh, irtt's functionality is basically a superset of netperf's UDP_RR. So automatically picking irtt if available and a fallback is the right thing to do, I think. I'd just add the plots everywhere, and if OWD data is not available, those plots would just be empty. Same thing we do for TCP window stats currently. Longer term, maybe hiding the plots entirely when there is no data is better, but for now empty plots are fine. > Personally I don't think it's necessary to check for server-side > support. If someone is specifying they want to use a particular tool, > I think they're declaring that it's available, as it is today with > netperf / netserver. Yes, but if we do automatic detection with a preference we could get into the situation where irtt exists on the client but the test is being run against a server that doesn't have it. This is especially likely to happen before the *.netperf.bufferbloat.net servers have irtt deployed. Could you be persuaded to add a 'check_server' action to irtt? Something that just does the handshake and doesn't run any more tests other than that. Then we could have Flent call that to verify that irtt is usable... -Toke -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/tohojo/flent/issues/106#issuecomment-344905911 [-- Attachment #1.2: Type: text/html, Size: 7980 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
next prev parent reply other threads:[~2017-11-16 12:16 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <tohojo/flent/issues/106@github.com> 2017-09-26 9:41 ` Toke Høiland-Jørgensen 2017-09-26 18:35 ` Toke Høiland-Jørgensen 2017-10-10 9:08 ` Toke Høiland-Jørgensen 2017-10-15 17:18 ` Toke Høiland-Jørgensen 2017-10-16 15:54 ` Toke Høiland-Jørgensen 2017-10-31 11:12 ` Toke Høiland-Jørgensen 2017-10-31 12:02 ` Toke Høiland-Jørgensen 2017-11-16 9:57 ` Toke Høiland-Jørgensen 2017-11-16 12:15 ` Toke Høiland-Jørgensen [this message] 2017-11-16 12:17 ` Toke Høiland-Jørgensen 2017-11-16 12:48 ` Toke Høiland-Jørgensen 2017-11-16 13:07 ` Toke Høiland-Jørgensen 2017-11-16 13:18 ` Toke Høiland-Jørgensen 2017-11-16 14:47 ` Toke Høiland-Jørgensen 2017-11-16 18:09 ` Toke Høiland-Jørgensen 2017-11-16 18:11 ` Toke Høiland-Jørgensen 2017-11-17 14:58 ` Toke Høiland-Jørgensen 2017-11-18 13:04 ` Toke Høiland-Jørgensen [not found] ` <tohojo/flent/issues/106/345442147@github.com> 2017-11-18 19:07 ` Dave Taht 2017-11-20 12:11 ` Toke Høiland-Jørgensen 2017-11-20 13:21 ` Toke Høiland-Jørgensen 2017-11-20 21:14 ` Dave Taht 2017-11-20 21:44 ` Dave Taht 2017-11-20 16:01 ` Toke Høiland-Jørgensen 2017-11-20 20:58 ` Toke Høiland-Jørgensen 2017-11-21 10:36 ` Toke Høiland-Jørgensen 2017-11-21 14:53 ` Toke Høiland-Jørgensen 2017-11-21 21:56 ` Toke Høiland-Jørgensen 2017-11-22 7:49 ` Toke Høiland-Jørgensen 2017-11-22 12:03 ` Toke Høiland-Jørgensen 2017-11-22 12:05 ` Toke Høiland-Jørgensen 2017-11-22 12:06 ` Toke Høiland-Jørgensen 2017-11-22 13:34 ` Toke Høiland-Jørgensen 2017-11-22 21:57 ` Toke Høiland-Jørgensen [not found] ` <tohojo/flent/issues/106/332043470@github.com> 2017-11-26 16:49 ` Matthias Tafelmeier
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/106/344905911@github.com \ --to=notifications@github.com \ --cc=comment@noreply.github.com \ --cc=flent-users@flent.org \ --cc=flent@noreply.github.com \ --cc=reply+01ead4bfc317ff573a5304fe5a887277d15bfc866531663792cf000000011625437192a169ce0ceefa50@reply.github.com \ --subject='Re: [Flent-users] [tohojo/flent] packet loss stats (#106)' \ /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