From: Rich Brown <notifications@github.com>
To: tohojo/flent <flent@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: Re: [Flent-users] [tohojo/flent] Incorrect "TCP upload sum" for tcp_nup, rrul, rrul_be tests (#182)
Date: Fri, 13 Sep 2019 18:15:16 -0700 [thread overview]
Message-ID: <tohojo/flent/issues/182/531433159@github.com> (raw)
In-Reply-To: <tohojo/flent/issues/182@github.com>
[-- Attachment #1.1: Type: text/plain, Size: 2803 bytes --]
Sorry to re-open, but the new version (Flent 1.9.9-git-ff46520) seems to fix the upload values for the Average - the individual streams sum to the displayed sum.
But the Median values still don't look right. Here are two runs of the same command:
```
bash-3.2$ flent -x -L -H flent-fremont.bufferbloat.net -t "flent-fremont.bufferbloat.net" --te=upload_streams=4 --te=ping_hosts=1.1.1.1 tcp_nup
Started Flent 1.9.9-git-ff46520 using Python 3.7.4.
Starting tcp_nup test. Expected run time: 70 seconds.
Data file written to ./tcp_nup-2019-09-13T210706.195971.flent-fremont_bufferbloat_net.flent.gz.
Summary of tcp_nup test run from 2019-09-14 01:07:06.195971
Title: 'flent-fremont.bufferbloat.net'
avg median # data pts
Ping (ms) ICMP : 101.23 101.00 ms 347
Ping (ms) ICMP 1.1.1.1 (extra) : 23.39 23.90 ms 347
TCP upload avg : 0.17 0.18 Mbits/s 354
TCP upload sum : 0.69 0.30 Mbits/s 354
TCP upload::1 : 0.16 0.17 Mbits/s 354
TCP upload::2 : 0.15 0.14 Mbits/s 354
TCP upload::3 : 0.19 0.20 Mbits/s 354
TCP upload::4 : 0.19 0.20 Mbits/s 354
```
```
bash-3.2$ flent -x -L -H flent-fremont.bufferbloat.net -t "flent-fremont.bufferbloat.net" --te=upload_streams=4 --te=ping_hosts=1.1.1.1 tcp_nup
Started Flent 1.9.9-git-ff46520 using Python 3.7.4.
Starting tcp_nup test. Expected run time: 70 seconds.
Data file written to ./tcp_nup-2019-09-13T211010.793062.flent-fremont_bufferbloat_net.flent.gz.
Summary of tcp_nup test run from 2019-09-14 01:10:10.793062
Title: 'flent-fremont.bufferbloat.net'
avg median # data pts
Ping (ms) ICMP : 102.19 102.00 ms 347
Ping (ms) ICMP 1.1.1.1 (extra) : 24.91 24.80 ms 341
TCP upload avg : 0.15 0.16 Mbits/s 354
TCP upload sum : 0.62 0.16 Mbits/s 354
TCP upload::1 : 0.12 0.13 Mbits/s 354
TCP upload::2 : 0.18 0.19 Mbits/s 354
TCP upload::3 : 0.18 0.19 Mbits/s 354
TCP upload::4 : 0.14 0.15 Mbits/s 354
bash-3.2$
```
--
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/182#issuecomment-531433159
[-- Attachment #1.2: Type: text/html, Size: 4205 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-14 1:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 12:03 Rich Brown
2019-09-12 12:09 ` Rich Brown
2019-09-13 16:13 ` Toke Høiland-Jørgensen
2019-09-13 16:13 ` Toke Høiland-Jørgensen
2019-09-14 1:15 ` Rich Brown [this message]
2019-09-14 15:39 ` 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/182/531433159@github.com \
--to=notifications@github.com \
--cc=flent@noreply.github.com \
--cc=reply+AHVNJPZMGMEH3WU6JIS5M3V3RF73JEVBNHHB2XXUKY@reply.github.com \
--cc=subscribed@noreply.github.com \
--subject='Re: [Flent-users] [tohojo/flent] Incorrect "TCP upload sum" for tcp_nup, rrul, rrul_be tests (#182)' \
/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