Flent-users discussion archives
 help / color / mirror / Atom feed
From: Sourabh jain <jainsourabh679@gmail.com>
To: flent-users@flent.org
Subject: [Flent-users] Query regarding TCP throughput behavior
Date: Wed, 2 May 2018 11:28:05 +0530	[thread overview]
Message-ID: <CACorBCBO0oB8wcLxzWbRyL_AROz+vqA_ChdQS1cPwtCVhj=BiQ@mail.gmail.com> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 571 bytes --]

Hello All,

I have a query regarding TCP upload result. I was running Flent on a
testbed of four nodes connected serially.

Flent Client: n1
netserver:    n4
TCP used:   BIC
Test length: 30

I ran tcp_2up test and observed that one flow starts with high throughput
and other with low (available in attachment). In my opinion, both should
start from low throughput and grow higher (because of slow start algorithm).

I want to know that, what are the reasons behind such behavior?

Thanks and Regards,
Sourabh Jain

[-- Attachment #1.2: Type: text/html, Size: 819 bytes --]

[-- Attachment #2: uploadbandwidth.png --]
[-- Type: image/png, Size: 69420 bytes --]

[-- Attachment #3: Type: text/plain, Size: 151 bytes --]

Flent-users mailing list

                 reply	other threads:[~2018-05-02  5:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

  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='CACorBCBO0oB8wcLxzWbRyL_AROz+vqA_ChdQS1cPwtCVhj=BiQ@mail.gmail.com' \
    --to=jainsourabh679@gmail.com \
    --cc=flent-users@flent.org \
    --subject='Re: [Flent-users] Query regarding TCP throughput behavior' \


* 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