From: Jonathan Morton <chromatix99@gmail.com>
To: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] facebook releases network test tool for slow and dodgy conditions
Date: Tue, 24 Mar 2015 22:03:44 +0200 [thread overview]
Message-ID: <40167760-F680-4D96-884C-586362446C48@gmail.com> (raw)
In-Reply-To: <20150324195715.GA22175@sesse.net>
> On 24 Mar, 2015, at 21:57, Steinar H. Gunderson <sgunderson@bigfoot.com> wrote:
>
> On Tue, Mar 24, 2015 at 03:49:42PM -0400, Rich Brown wrote:
>> I hope they *do* have bufferbloat in their emulator. It'd be a real shame
>> if they failed to mimic the presence of bufferbloat in 3G/4G/DSL/etc.
>> uplinks. Imagine if everyone developed their app using ATC, then wondered
>> why their performance stinks in the real world...
>
> Does the distinction between “low-throughput, low-latency” and
> “low-throughput, low-latency, bufferbloated” really mean all that much for
> the average userspace app? You have to go pretty deep in the stack before the
> _reason_ for the slowness matters much.
I’d say that there’s a useful distinction between “low throughput, *high* latency” and “low throughput, low latency, bufferbloat”. The distinction between the two cases you mention should be obvious to everyone here, of course.
The distinction between general high latency and bufferbloat-induced latency is that you can potentially mitigate the latter at the application level, by opening fewer connections or performing manual congestion control. This assumes that you’re the only application using the link, but it’s better than nothing.
- Jonathan Morton
prev parent reply other threads:[~2015-03-24 20:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 19:09 Dave Taht
2015-03-24 19:26 ` Dave Taht
2015-03-24 19:49 ` Rich Brown
2015-03-24 19:57 ` Steinar H. Gunderson
2015-03-24 20:03 ` Jonathan Morton [this message]
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=40167760-F680-4D96-884C-586362446C48@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=sgunderson@bigfoot.com \
/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