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: Sat, 18 Nov 2017 13:04:45 +0000 (UTC) [thread overview] Message-ID: <tohojo/flent/issues/106/345441084@github.com> (raw) In-Reply-To: <tohojo/flent/issues/106@github.com> [-- Attachment #1.1: Type: text/plain, Size: 1496 bytes --] On 18 November 2017 13:43:23 CET, Pete Heist <notifications@github.com> wrote: >Maybe of interest, the per-packet upstream vs downstream loss now works >properly, if you want to use it. Limitations documented: >https://github.com/peteheist/irtt#64-bit-received-window > >But how to plot that. Maybe there could be an up arrow for `lost_up`, >down arrow for `lost_down`, or X for the generic `lost` shown at y=0 on >the latency plot, along with a gap in the plotted line? Yeah, currently I'm skipping drops entirely, which is probably not the right thing to do. Same with the ping runner. Will think about how to fix that. On a separate plot, drops could just be plotted as a "drops per interval" plot. That's what the qdisc stats plot does. >IRTT for the voip tests would be awesome! (I hope) Just an idea, >instead of having separate voip tests, any of the tests with UDP flows >could become a voip test by accepting a "voip_codec" test-parameter >that sets the interval and packet length. Common codec values: >https://www.cisco.com/c/en/us/support/docs/voice/voice-quality/7934-bwidth-consume.html#anc1 > >I guess having generic parameters to explicitly set interval and packet >length would still be useful... Are VoIP packets always straight fixed interval? Or would you need to support various distributions? -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-345441084 [-- Attachment #1.2: Type: text/html, Size: 4674 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-18 13:05 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 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 [this message] [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/345441084@github.com \ --to=notifications@github.com \ --cc=comment@noreply.github.com \ --cc=flent-users@flent.org \ --cc=flent@noreply.github.com \ --cc=reply+01ead4bf009c8c5848fbf300a0f0619430111c9fa81f201092cf000000011627f1ed92a169ce0ceefa50@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