From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] facebook releases network test tool for slow and dodgy conditions
Date: Tue, 24 Mar 2015 20:57:15 +0100 [thread overview]
Message-ID: <20150324195715.GA22175@sesse.net> (raw)
In-Reply-To: <4FEFA225-B30F-40E2-8594-BDBF1D9F3DFB@gmail.com>
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.
/* Steinar */
--
Homepage: http://www.sesse.net/
next prev parent reply other threads:[~2015-03-24 19:57 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 [this message]
2015-03-24 20:03 ` Jonathan Morton
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=20150324195715.GA22175@sesse.net \
--to=sgunderson@bigfoot.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