From: olg33 <notifications@github.com>
To: tohojo/flent <flent@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [Flent-users] [tohojo/flent] rrul tests are not being able to saturate link (#218)
Date: Mon, 14 Dec 2020 16:12:00 -0800 [thread overview]
Message-ID: <tohojo/flent/issues/218@github.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]
Hi,
We are installing a new satellite link and we are using flent to run bandwidth testing. The idea is to saturate the link with marked and unmarked packets.
However initial results show that the test was not able to reach the maximum bandwidth downstream supported by the link which is about 60Mbps.
For unmarked traffic we ran the following test:
`flent rrul -H 10.111.40.252`
For marked traffic we used the following test:
`flent rrul_var -H 10.111.40.252 --test-parameter bidir_streams=5 --test-parameter markings=11,13,15,19,21 `
On both cases we reached no more than 50% of the link capacity.
To rule out any problem with the link itself, we ran the following test:
`flent tcp_12down -H 10.111.40.252`
This time. we were able to reach saturation levels (60Mbps) of downstream traffic. Also ran iperf3 and obtained the same results
Do you see any reason why the rrul and rrul_var tests aren't being able to generate enough traffic to saturate the link? Maybe any parameter I'm missing or something? Or maybe that's normal, anyhow, I'd appreciate any comment on this matter.
Thanks.
--
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/218
[-- Attachment #2: Type: text/html, Size: 2204 bytes --]
next reply other threads:[~2020-12-15 0:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 0:12 olg33 [this message]
2020-12-15 11:37 ` [Flent-users] " Toke Høiland-Jørgensen
2020-12-15 22:19 ` olg33
2020-12-17 23:01 ` olg33
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@github.com \
--to=notifications@github.com \
--cc=flent@noreply.github.com \
--cc=reply+AHVNJP4SPDMKTBOJS2GL5IN54PQFBEVBNHHC3OAZRU@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