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] completion delay for an iperf script (#138)
Date: Mon, 11 Jun 2018 02:36:30 -0700 [thread overview]
Message-ID: <tohojo/flent/issues/138/396183133@github.com> (raw)
In-Reply-To: <tohojo/flent/issues/138@github.com>
[-- Attachment #1.1: Type: text/plain, Size: 1377 bytes --]
Matthieu Coudron <notifications@github.com> writes:
> `Yeah, this is an issue with netperf; it'll only output time in 10-ms`
>
> thanks for pointing this out. Not that useful for intra datacenter
> latencies then. My final tests should effectively longer but it's nice
> to iterate over shorter transfers.
Well it's more a function of the transfer size, but yeah, this is a bit
annoying...
> `To get multiple datapoints, you'd need to run multiple tests (`for s
> in $(seq 10); do flent <args>; done`), then plot all data files at
> once.`
>
> But each run will be recorded in a different .flent.gz ? which goes
> back to my initial question, how can I plot data directly from the
> flent.gz without re-running the tests ?
Yes. If you want to collect several data points in a single .flent.gz,
the timeseries aggregator is not going to work. You'll have to use the
iteration aggregator (set AGGREGATOR='iteration' in the test config
file), and use a different runner that outputs the ELAPSED_TIME as a
single data point. I think it should be enough to subclass the
netperfdemorunner, and redefine parse() to call the parent, pull out the
ELAPSED_TIME metadata, and return that.
-Toke
--
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/138#issuecomment-396183133
[-- Attachment #1.2: Type: text/html, Size: 5927 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:[~2018-06-11 9:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tohojo/flent/issues/138@github.com>
2018-06-07 8:57 ` Toke Høiland-Jørgensen
2018-06-07 10:01 ` Toke Høiland-Jørgensen
2018-06-08 10:20 ` Toke Høiland-Jørgensen
2018-06-08 10:55 ` Toke Høiland-Jørgensen
2018-06-11 9:15 ` Toke Høiland-Jørgensen
2018-06-11 9:36 ` Toke Høiland-Jørgensen [this message]
2018-06-11 12:20 ` Toke Høiland-Jørgensen
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/138/396183133@github.com \
--to=notifications@github.com \
--cc=flent@noreply.github.com \
--cc=reply+01ead4bf2ebba0c0cea1c079d35a98ff48324fe57dd1372892cf000000011736049e92a169ce13aceaa7@reply.github.com \
--cc=subscribed@noreply.github.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