[Bloat] facebook releases network test tool for slow and dodgy conditions

[Bloat] facebook releases network test tool for slow and dodgy conditions

[Dave Taht]

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

Re: [Bloat] facebook releases network test tool for slow and dodgy conditions

[Dave Taht]

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

Re: [Bloat] facebook releases network test tool for slow and dodgy conditions

[Rich Brown]

[-- 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 --]

Re: [Bloat] facebook releases network test tool for slow and dodgy conditions

[Steinar H. Gunderson]

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/

Re: [Bloat] facebook releases network test tool for slow and dodgy conditions

[Jonathan Morton]

> 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