Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Rich Brown <richb.hanover@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] facebook releases network test tool for slow and dodgy conditions
Date: Tue, 24 Mar 2015 15:49:42 -0400	[thread overview]
Message-ID: <4FEFA225-B30F-40E2-8594-BDBF1D9F3DFB@gmail.com> (raw)
In-Reply-To: <CAA93jw5z4ie7N=KOmGk6dcsrU0WRCGR1OiSxquR3JPcSUkyMpw@mail.gmail.com>

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

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...


On Mar 24, 2015, at 3:26 PM, Dave Taht <dave.taht@gmail.com> wrote:

> Well, I looked, (Wet paint!) and filed bugs. Sigh:
> https://github.com/facebook/augmented-traffic-control/issues/60
> 
> Maybe with a rename of netperf-wrapper, a press release from a redhat
> or google, and coverage in slashdot, we´d get 107 forks and 1048 stars
> on github, and some more contributors, testers, tests, and patches.
> 
> On Tue, Mar 24, 2015 at 12:09 PM, Dave Taht <dave.taht@gmail.com> wrote:
>> as seen on slashdot...
>> 
>> 
>> http://tech.slashdot.org/story/15/03/24/0332206/facebook-engineering-tool-mimics-dodgy-network-connectivity
>> 
>> doc and code:
>> 
>> http://facebook.github.io/augmented-traffic-control/
>> 
>> I do hope they got the bloat emulation right. I am afraid to look.
>> (and too busy today, besides). Anyone got a bit of time to look this
>> over?
>> 
>> --
>> Dave Täht
>> Let's make wifi fast, less jittery and reliable again!
>> 
>> https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
> 
> 
> 
> -- 
> Dave Täht
> Let's make wifi fast, less jittery and reliable again!
> 
> https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 496 bytes --]

      reply	other threads:[~2015-03-24 19:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 19:09 [Cerowrt-devel] " Dave Taht
2015-03-24 19:26 ` Dave Taht
2015-03-24 19:49   ` Rich Brown [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/cerowrt-devel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=4FEFA225-B30F-40E2-8594-BDBF1D9F3DFB@gmail.com \
    --to=richb.hanover@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.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