Flent-users discussion archives
 help / color / mirror / Atom feed
From: Emmanuel Blot <eblot.ml@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: flent-users@flent.org
Subject: Re: [Flent-users] Help with RRUL / TCP upload
Date: Mon, 31 Jul 2017 22:11:13 +0200	[thread overview]
Message-ID: <CAKJJEPzvXswJGW0KXRAxWqt=CuzXhQvQ6DnjM1ZiBNPuLDFKZg@mail.gmail.com> (raw)
In-Reply-To: <35FBAAE5-FE6E-4D48-9884-B5AF7455A529@gmx.de>


[-- Attachment #1.1.1: Type: text/plain, Size: 2152 bytes --]

Hi Sebastian,

Following your recommandations, I tried with several step-size values, with
no luck.
It does not seem to help the TCP upload graph.

I do not want to bother ML users with the graphs, I copy them to Dropbox:

https://www.dropbox.com/s/qxrdxvtqs7d6hfp/stepsize0.1.png?dl=0
https://www.dropbox.com/s/j54gaofor3ktjyt/stepsize0.5.png?dl=0
https://www.dropbox.com/s/i5fdqwldabx0820/stepsize0.05.png?dl=0
https://www.dropbox.com/s/dxf0ihlghy50d8b/stepsize1.png?dl=0

Thanks for your help,
Manu.


On Mon, Jul 31, 2017 at 8:13 PM, Sebastian Moeller <moeller0@gmx.de> wrote:

> Hi,
>
> I believe you need to set the step size to something bigger:
> from "run-flent --help"
> -s STEP_SIZE, --step-size STEP_SIZE
>                         Measurement data point step size.
>
> For a slow link there are simply no data from netperf for a given
> "sampling" point and hence you get the intermittent plots. As far as I know
> there is unfortunately no way to specify the step size independent for both
> directions, so for non-choppy plots in your slow direction you will also
> get less time resolution in your fast direction...
>
> Hope that helps
>
>
>
>
> On Jul 31, 2017, at 19:36, Emmanuel Blot <eblot.ml@gmail.com> wrote:
>
> Hi all,
>
> I’m a new flent user.
>
> I’m trying to check my SQM settings on OpenWRT against bufferbloat.
>
> For some reason, the TCP download and ping graphs for RRUL sessions
> give sensible results, whereas the TCP upload is broken into very
> small segments (even closer to dots actually), see the attached
> sample.
>
> What am I doing wrong ?
>
> command line: flent rrul -p all_scaled -l 60 -H host -o output.png
>
> $ flent --version
> Flent v1.0.1.
> Running on Python 3.5.2 (default, Oct 11 2016, 04:59:56)  [GCC 4.2.1
> Compatible Apple LLVM 8.0.0 (clang-800.0.38)].
> Using matplotlib version 2.0.1 on numpy 1.12.1.
> Using PyQt5 version 5.9.
>
>
> Thanks,
> Manu.
> _______________________________________________
> Flent-users mailing list
> Flent-users@flent.org
> http://flent.org/mailman/listinfo/flent-users_flent.org
>
>
>

[-- Attachment #1.1.2: Type: text/html, Size: 3560 bytes --]

[-- Attachment #1.2: tcp_upload.png --]
[-- Type: image/png, Size: 22024 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:[~2017-07-31 20:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-31 17:36 Emmanuel Blot
2017-07-31 18:13 ` Sebastian Moeller
2017-07-31 20:11   ` Emmanuel Blot [this message]

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='CAKJJEPzvXswJGW0KXRAxWqt=CuzXhQvQ6DnjM1ZiBNPuLDFKZg@mail.gmail.com' \
    --to=eblot.ml@gmail.com \
    --cc=flent-users@flent.org \
    --cc=moeller0@gmx.de \
    --subject='Re: [Flent-users] Help with RRUL / TCP upload' \
    /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