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] RRUL Upload plot - why such low granularity? (#185) Date: Thu, 19 Sep 2019 11:13:39 -0700 [thread overview] Message-ID: <tohojo/flent/issues/185/533247772@github.com> (raw) In-Reply-To: <tohojo/flent/issues/185@github.com> [-- Attachment #1.1: Type: text/plain, Size: 2435 bytes --] Rich Brown <notifications@github.com> writes: >> Basically, the problem is the way netperf determines its data output intervals in demo mode: > > Ahah! That was the explanation, but I wasn't (yet) smart enough to > comprehend it. [To further test out my understanding... If netperf > were to use a smaller "data output interval" when it's transmitting, > it would create more frequent updates and the granularity would be > higher...] > > But I'm not sure that fully explains it unless netperf uses a (very) > different data output interval for receiving... The download chart has > hundreds of points, while the ratio between my download and upload is > about 10:1 (7mbps vs 768kbps) so I'd expect the upload chart to have > something like dozens of points... This is because netperf only checks whether it should output a data point after it has sent a certain number of bytes. 16k in your case (it's in the series metdata). At 768kbps, 16k bytes takes ~2.6 seconds to send, so you'll get at most one data point for every such interval. Now that I'm looking at this again, it seems that you can actually set the send size. However, lowering it naturally impacts CPU usage. A quick test on my laptop indicates that lowering it to 512 bytes raises netperf's CPU usage from ~2% to ~20% for a single flow at half a gigabit. So yeah, we could probably lower it somewhat, but to what? We can't know ahead of time what connection speed we will be running on. If you want to try a quick test with a smaller size, this patch (to Flent) adds the option unconditionally; obviously not the right way to go about it, but it should allow you to test the impact at least: diff --git a/flent/runners.py b/flent/runners.py index a75223d..3d5e373 100644 --- a/flent/runners.py +++ b/flent/runners.py @@ -1049,6 +1049,7 @@ class NetperfDemoRunner(ProcessRunner): "{marking} -H {control_host} -p {control_port} " \ "-t {test} -l {length:d} {buffer} {format} " \ "{control_local_bind} {extra_args} -- " \ + "-m 512,512 " \ "{socket_timeout} {local_bind} -H {host} -k {output_vars} " \ "{cong_control} {extra_test_args}".format(**args) -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/tohojo/flent/issues/185#issuecomment-533247772 [-- Attachment #1.2: Type: text/html, Size: 4130 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:[~2019-09-19 18:14 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <tohojo/flent/issues/185@github.com> 2019-09-19 14:59 ` Toke Høiland-Jørgensen 2019-09-19 18:13 ` Toke Høiland-Jørgensen [this message] 2019-09-29 18:44 ` Toke Høiland-Jørgensen 2019-09-29 19:05 ` Sebastian Moeller 2019-09-29 19:08 ` Toke Høiland-Jørgensen 2019-09-29 19:34 ` Sebastian Moeller
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/185/533247772@github.com \ --to=notifications@github.com \ --cc=comment@noreply.github.com \ --cc=flent-users@flent.org \ --cc=flent@noreply.github.com \ --cc=reply+AHVNJPZIBED4U62TX555ESN3SD35HEVBNHHB3DQ34A@reply.github.com \ --subject='Re: [Flent-users] [tohojo/flent] RRUL Upload plot - why such low granularity? (#185)' \ /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