General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Aaron Wood <woody77@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] fq_codel, high bandwidth, and delays
Date: Mon, 7 Jul 2014 21:10:48 -0700	[thread overview]
Message-ID: <CALQXh-MYQbssEh8gQQr85uMT5AyJRFAvCGVecNoqoeoSTKi+kg@mail.gmail.com> (raw)

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

List,

In talking with a friend over the weekend that moves data around for the
national labs (on links at rates like 10Gbps), we ended up having a rather
interesting discussion about just how radically different the problem
spaces are vs. what he's seen in the bufferbloat community.

They have few flows, long lived, and are trying to push >1Gbps per flow,
across the continent (or from Europe to the US), with inherent delays on
the order of 100ms.  TCP under these conditions is, from his reports,
incredibly fragile, where even a tiny packet error rate stops TCP for
saturating the link (since it can't tell the difference between congestion
and a non-congestion-related dropped packet).

And suddenly the "every packet is precious" mode of thought becomes crystal
clear.

Clearly they are trying to solve different problems, yet they do have
congestion events, when new flows are added to the network.

Has anyone used fq_codel (or it's friends) in scenarios like this?  fq is
fairly new (2 years?) and I can't find much about it and high bandwidth
links in my searches.

Given that their problems aren't those that fq is trying to solve, I
wouldn't expect it, but curious to see if anyone has any research on it.

Thanks,
Aaron

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

             reply	other threads:[~2014-07-08  4:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08  4:10 Aaron Wood [this message]
2014-07-08  4:38 ` David Lang
2014-07-11  6:20 ` Neil Davies
     [not found] <mailman.1.1404846002.28466.bloat@lists.bufferbloat.net>
2014-07-08 19:43 ` David Collier-Brown
2014-07-08 20:35   ` David Lang

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-MYQbssEh8gQQr85uMT5AyJRFAvCGVecNoqoeoSTKi+kg@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