Flent-users discussion archives
 help / color / mirror / Atom feed
From: olg33 <notifications@github.com>
To: tohojo/flent <flent@noreply.github.com>
Cc: flent-users <flent-users@flent.org>,
	Comment <comment@noreply.github.com>
Subject: [Flent-users] Re: [tohojo/flent] rrul tests are not being able to saturate link (#218)
Date: Thu, 17 Dec 2020 15:01:33 -0800	[thread overview]
Message-ID: <tohojo/flent/issues/218/747752860@github.com> (raw)
In-Reply-To: <tohojo/flent/issues/218@github.com>

[-- Attachment #1: Type: text/plain, Size: 3913 bytes --]


In a related issue, It took our attention that whenever we run a rrul or rrul_var test, upload traffic seems to be absent.

Below examples were performed with two servers connected back-to-back with no router in between to rule out any blockage (they connect using an ethernet switch with ports in the same Vlan).
 
 `$ flent rrul_var -H 172.16.1.40 --test-parameter bidir_streams=6 --test-parameter markings=11,13,15,17,19,21`

Summary of rrul_var test run from 2020-12-17 21:34:16.260047

 Ping (ms) avg         :             2.65          N/A ms              350
 Ping (ms)::ICMP       :            6.62         8.37 ms              350
 Ping (ms)::UDP 0 (11) :         1.99         0.14 ms              350
 Ping (ms)::UDP 1 (13) :         1.98         0.14 ms              350
 Ping (ms)::UDP 2 (15) :         1.96         0.14 ms              350
 Ping (ms)::UDP 3 (17) :         2.00         0.14 ms              350
 Ping (ms)::UDP 4 (19) :         2.00         0.14 ms              350
 Ping (ms)::UDP 5 (21) :         1.99         0.14 ms              350
 TCP download avg      :       156.53          N/A Mbits/s          350
 TCP download sum      :       939.18          N/A Mbits/s          350
 TCP download::0 (11)  :       190.43       171.36 Mbits/s         350  ---> OK
 TCP download::1 (13)  :       166.60       170.35 Mbits/s         350
 TCP download::2 (15)  :       143.99       156.95 Mbits/s         350
 TCP download::3 (17)  :       171.11       170.65 Mbits/s         350
 TCP download::4 (19)  :       110.92        94.05 Mbits/s         350
 TCP download::5 (21)  :       156.13         0.01 Mbits/s         350
 TCP totals            :              939.87          N/A Mbits/s         350
 TCP upload avg        :         0.12               N/A Mbits/s         350
 TCP upload sum        :        0.69               N/A Mbits/s         350
 TCP upload::0 (11)    :         0.19              0.18 Mbits/s         350  ---> No data
 TCP upload::1 (13)    :         0.10              0.17 Mbits/s         350
 TCP upload::2 (15)    :         0.04              0.07 Mbits/s         350
 TCP upload::3 (17)    :         0.14              0.13 Mbits/s         350
 TCP upload::4 (19)    :         0.09              0.13 Mbits/s         350
 TCP upload::5 (21)    :         0.13              0.14 Mbits/s         350

Now, if we run a tcp_12up test, we see upstream traffic:

 Ping (ms) ICMP :        2.22         2.55 ms                  350
 TCP upload avg :       41.77          N/A Mbits/s          350
 TCP upload sum :     501.25          N/A Mbits/s         350
 TCP upload::1  :        38.43        38.24 Mbits/s          350
 TCP upload::10 :        40.92        39.39 Mbits/s         350
 TCP upload::11 :        42.97        41.55 Mbits/s         350
 TCP upload::12 :        46.13        39.80 Mbits/s         350
 TCP upload::2  :        46.77        44.63 Mbits/s         350
 TCP upload::3  :        40.24        39.21 Mbits/s         350
 TCP upload::4  :        40.75        40.54 Mbits/s         350
 TCP upload::5  :        40.41        38.85 Mbits/s         350
 TCP upload::6  :        42.30        40.38 Mbits/s         350
 TCP upload::7  :        41.68        40.38 Mbits/s         350
 TCP upload::8  :        40.70        39.47 Mbits/s         350
 TCP upload::9  :        39.95        40.17 Mbits/s         350

Apparently, on bi-directional tests, upload traffic doesn't show, but if we run a Upsteram-only test, it works.  

Traffic graphs on port connecting the servers show that indeed there is not Upstream traffic during testing.

Upload traffic must be present, otherwise how the second server is replying?

 Is there any way to make upload traffic show up on rrul testing?


Thanks.

-- 
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/218#issuecomment-747752860

[-- Attachment #2: Type: text/html, Size: 5002 bytes --]

  parent reply	other threads:[~2020-12-17 23:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-15  0:12 [Flent-users] " olg33
2020-12-15 11:37 ` [Flent-users] " Toke Høiland-Jørgensen
2020-12-15 22:19 ` olg33
2020-12-17 23:01 ` olg33 [this message]
2020-12-17 23:13 ` Toke Høiland-Jørgensen
2020-12-18 17:45 ` olg33
2021-01-13 17:24 ` 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/218/747752860@github.com \
    --to=notifications@github.com \
    --cc=comment@noreply.github.com \
    --cc=flent-users@flent.org \
    --cc=flent@noreply.github.com \
    --cc=reply+AHVNJP3UPCVHARM6QKWL6CN547CE3EVBNHHC3OAZRU@reply.github.com \
    --subject='[Flent-users] Re: [tohojo/flent] rrul tests are not being able to saturate link (#218)' \
    /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