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] completion delay for an iperf script (#138)
Date: Thu, 07 Jun 2018 01:57:22 -0700	[thread overview]
Message-ID: <tohojo/flent/issues/138/395346008@github.com> (raw)
In-Reply-To: <tohojo/flent/issues/138@github.com>


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

Matthieu Coudron <notifications@github.com> writes:

> I would like to send a fixed amount of data (I am more used to iperf)
> so for instance run 10 times ` iperf -c HOST -n 6MB` and show a cdf of
> the completion times.

Hmm, so what is it that you are trying to measure here? This doesn't
sound like it's a timeseries data series? You just want to repeat a
single download and measure its time, or are you planning to run another
bulk flow or latency measurement at the same time.
>
> I kinda understand the .conf format and came up with my own script iperf_cdf.conf
> ```
> DESCRIPTION="iperf completion delay 6MB"
> DEFAULTS={'PLOT': "iperf_delay",
>           'HOSTS': []}
>
> IPERF_V6=""
> if IP_VERSION == 6:
>     IPERF_V6="-V"
>
>
> DATA_SETS = o([
>     ('TCP iperf',
>         # -n => fixed number of byte
>          {'command': "iperf -c %s -i %.2f -y C -n 6M %s" % (HOST, max(0.5,STEP_SIZE), IPERF_V6),
>           'delay': DELAY,               # do I need this anymore ?
>           'units': 'second',
>           'runner': 'iperf_csv',})
>     ])

This will get you the iperf CSV output (i.e., bandwidth over time).

> Just for info here is the output.
> ```
> iperf -n 6M -c localhost --enhancedreports
> ------------------------------------------------------------
> Client connecting to localhost, TCP port 5001 with pid 20613
> Write buffer size:  128 KByte
> TCP window size: 2.50 MByte (default)
> ------------------------------------------------------------
> [  3] local 127.0.0.1 port 46618 connected with 127.0.0.1 port 5001
> [ ID] Interval        Transfer    Bandwidth       Write/Err  Rtry    Cwnd/RTT
> [  3] 0.00-0.23 sec  6.00 MBytes   221 Mbits/sec  1/0      65483        0K/56811 us
> ```

Yeah, there's no parser for this currently. But could probably be added,
either to the existing iperf parser, or another runner. Depends a bit on
what data you want; see my question above.

> NB: can I load this  iperf_cdf.conf out of tree ?

No. You can drop it in the tests folder, of course, but there is no
support for loading tests from an outside directory. Having this would
imply that the test format is API, which it isn't. So I'd much rather
include the test upstream; should be possible to parameterise it so it
is generally useful :)


-- 
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-395346008

[-- Attachment #1.2: Type: text/html, Size: 8571 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

       reply	other threads:[~2018-06-07  8:58 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 [this message]
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
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/395346008@github.com \
    --to=notifications@github.com \
    --cc=flent@noreply.github.com \
    --cc=reply+01ead4bf7219f560aa277b95d9212ed0e7dd5c80bbca01f592cf000000011730b57292a169ce13aceaa7@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