From: Dave Taht <dave.taht@gmail.com>
To: Azin Neishaboori <azin.neishaboori@gmail.com>
Cc: bloat-devel <bloat-devel@lists.bufferbloat.net>
Subject: Re: BBR performance on LTE
Date: Tue, 22 Jan 2019 13:07:03 -0800 [thread overview]
Message-ID: <CAA93jw6MRWi=ez0eLcZ-=UqsWfWhdKZyRcLonRKp534AwZrwYg@mail.gmail.com> (raw)
In-Reply-To: <CADXq5+9s-yA2-GpVdHR+my7Qk=69Rj86c3zNdS3NGFd-q81Gsw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 784 bytes --]
I am a huge believer in also seeing the baseline *.flent.gz files and other
plots you can get via the flent-gui... if you could post them somewhere or
send to me privately? Two examples are obtaining the baseline RTT,
and it would be my hope, over time, that BBR would have found the baseline
RTT later in the test (the up or down bandwidth plots) than is shown by
these summary plots. Also as much as I love the rrul tests for quickly
showing the characteristics of a link under load, BBR makes the assumption
that flows start up one at a time, and a better string of basic tests would
be to use tcp_nup or tcp_ndown.
From squinting... It looks like the *baseline* RTT in this test is ~200ms.
There really isn't much in this world that works particularly well with
RTTs this large.
[-- Attachment #2: Type: text/html, Size: 866 bytes --]
next prev parent reply other threads:[~2019-01-22 21:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 22:00 Azin Neishaboori
2019-01-22 15:39 ` Azin Neishaboori
2019-01-22 21:07 ` Dave Taht [this message]
2019-01-22 21:59 ` Azin Neishaboori
2019-01-22 22:00 ` Dave Taht
2019-01-22 22:27 ` [Bloat] " Sebastian Moeller
2019-01-22 22:31 ` Azin Neishaboori
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw6MRWi=ez0eLcZ-=UqsWfWhdKZyRcLonRKp534AwZrwYg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=azin.neishaboori@gmail.com \
--cc=bloat-devel@lists.bufferbloat.net \
/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