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] tcp_rtt plot doesn't seem to work with rrul_be_nflows (#116)
Date: Wed, 15 Nov 2017 16:41:38 +0000 (UTC) [thread overview]
Message-ID: <tohojo/flent/issues/116/344652188@github.com> (raw)
In-Reply-To: <tohojo/flent/issues/116@github.com>
[-- Attachment #1.1: Type: text/plain, Size: 1073 bytes --]
Pete Heist <notifications@github.com> writes:
> Hi, just noticed that when I run these commands there's no data plotted in the resulting plot title_tcp_rtt.png (copying from a script so this is just a rough idea of what I'm doing):
>
> ```
> flent rrul_be_nflows -l 60 -H 10.9.0.2 -p all_scaled \
> --figure-width=10 --figure-height=7.5 \
> --socket-stats \
> --test-parameter upload_streams=4 \
> --test-parameter download_streams=4 \
> -t title -o title.png
>
> flent -p tcp_rtt -i *.flent.gz -o title_tcp_rtt.png
> ```
>
> I just pulled this from the head to make sure. If I run an `rrul_be`
> test instead, the `tcp_rtt` plot does contain data as expected, so it
> seems like it's something with `rrul_be_nflows` that happens during
> plot generation. I can see `tcp_rtt` values in the .flent.gz file.
Could you attach the data file, please? Then I'll have a look :)
-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/116#issuecomment-344652188
[-- Attachment #1.2: Type: text/html, Size: 3794 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 parent reply other threads:[~2017-11-15 16:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tohojo/flent/issues/116@github.com>
2017-11-15 16:41 ` Toke Høiland-Jørgensen [this message]
2017-11-16 6:46 ` Toke Høiland-Jørgensen
2017-11-16 8:09 ` Pete Heist
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/116/344652188@github.com \
--to=notifications@github.com \
--cc=flent@noreply.github.com \
--cc=reply+01ead4bfabfa8fdf62d7063d56890415df97ae9ec2360d3b92cf000000011624304292a169ce10584ff0@reply.github.com \
--cc=subscribed@noreply.github.com \
--subject='Re: [Flent-users] [tohojo/flent] tcp_rtt plot doesn'\''t seem to work with rrul_be_nflows (#116)' \
/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