General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Aaron Wood <woody77@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] fremont flent node: what's the network setup there?
Date: Wed, 4 Oct 2017 22:41:44 -0700	[thread overview]
Message-ID: <CALQXh-PnEC-4GL5LzqKE-Ty_J8Cv+=Xp-tyo2nBbL7Pbs5Q9kQ@mail.gmail.com> (raw)

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

I'm comparing some numbers between the fremont node and a friend's Droplet
running netserver.

We've previous noted that we don't see more than a 120Mbps download rate
from the fremont node.

Today I was able to confirm in multiple back-to-back runs that the fremont
node was only giving me about 120Mbps of throughput, while both dslreports
and the droplet were giving me ~180Mbps (and 500ms of latency in the cable
head-end).

However, I noticed when running without SQM on my router here at home that
download latency from the fremont node was virtually non-existent, vs. the
very large latency that I was seeing from both the droplet and dsl-reports.

Box-plots:
https://drive.google.com/file/d/0B1xfqN4OiFEPODI4cEZjZ1NGeGVtc3RKbGJQR3ltaHhyb1Bz/view

That very, very low send latency from the fremont node makes me think that
it might be running BBR as the default congestion control algorithm?  If I
run the cubic-reno test without any SQM, the results look pretty awful, but
without specifying the TCP cc alg, it seems to behave very, very well
(albeit not as much throughput as I think I should get).

Re-enabling cake (at 170Mbps downstream, 12Mbps up), I can't seem to get
much more than that 120Mbps from the router (even though I've tested it at
900Mbps as the netserver host itself).  Am I running into a cpu limitation
in the NAT/forwarding modules?

-Aaron

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

             reply	other threads:[~2017-10-05  5:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-05  5:41 Aaron Wood [this message]
2017-10-05  6:39 ` Dave Taht

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.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CALQXh-PnEC-4GL5LzqKE-Ty_J8Cv+=Xp-tyo2nBbL7Pbs5Q9kQ@mail.gmail.com' \
    --to=woody77@gmail.com \
    --cc=bloat@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