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: Fri, 18 Dec 2020 09:45:28 -0800	[thread overview]
Message-ID: <tohojo/flent/issues/218/748226448@github.com> (raw)
In-Reply-To: <tohojo/flent/issues/218@github.com>

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

Hi tohojo,

Yes, I found the problem. The switch where our servers are connected had other servers and one of them had a port configured  by mistake the same Vlan of our piont-to-point connection. In principle that may not be a big deal, but once it was corrected I'm was able to push almost a Gig Up/Down:

 TCP download avg      :       133.64          N/A Mbits/s          351
 TCP download sum      :       935.50          N/A Mbits/s         351 ---------> OK
 TCP download::0 (11)  :       123.63       123.19 Mbits/s        351
 TCP download::1 (13)  :       121.54       121.51 Mbits/s        351
 TCP download::2 (15)  :       121.08       122.05 Mbits/s        351
 TCP download::3 (17)  :       121.59       121.58 Mbits/s        351
 TCP download::4 (19)  :        77.91        78.98 Mbits/s          351
 TCP download::5 (21)  :       244.72       244.05 Mbits/s        351
 TCP download::6 (25)  :       125.03       124.48 Mbits/s        351
 TCP totals            :            1871.57          N/A Mbits/s         351
 TCP upload avg        :       133.72          N/A Mbits/s           351
 TCP upload sum        :       936.07          N/A Mbits/s          351 ---------> OK
 TCP upload::0 (11)    :       135.29       134.01 Mbits/s         351
 TCP upload::1 (13)    :       134.59       134.75 Mbits/s         351
 TCP upload::2 (15)    :       131.10       131.34 Mbits/s         351
 TCP upload::3 (17)    :       131.24       131.24 Mbits/s         351
 TCP upload::4 (19)    :       134.21       134.62 Mbits/s         351
 TCP upload::5 (21)    :       134.76       134.69 Mbits/s         351
 TCP upload::6 (25)    :       134.88       134.74 Mbits/s         351
 

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-748226448

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

  parent reply	other threads:[~2020-12-18 17:45 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
2020-12-17 23:13 ` Toke Høiland-Jørgensen
2020-12-18 17:45 ` olg33 [this message]
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/748226448@github.com \
    --to=notifications@github.com \
    --cc=comment@noreply.github.com \
    --cc=flent-users@flent.org \
    --cc=flent@noreply.github.com \
    --cc=reply+AHVNJP2XGO37SOO4NF7PVY555DF3REVBNHHC3OAZRU@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