From: David Lang <david@lang.hm>
To: Valdis.Kletnieks@vt.edu
Cc: Neil Davies <neil.davies@pnsol.com>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] Check out www.speedof.me - no Flash
Date: Fri, 25 Jul 2014 16:30:29 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1407251626490.21739@nftneq.ynat.uz> (raw)
In-Reply-To: <25037.1406327367@turing-police.cc.vt.edu>
On Fri, 25 Jul 2014, Valdis.Kletnieks@vt.edu wrote:
> On Fri, 25 Jul 2014 14:20:53 -0700, David Lang said:
>
>> cost of bandwidth for this is just something to get someone to pay for (ideally
>> someone with tons of bandwidth already who won't notice this sort of test, even
>> if there are a few going on at once.)
>
> Ask U of Wisconsin how that worked out for them when Netgear shipped some
> new boxes....
>
> http://en.wikipedia.org/wiki/NTP_server_misuse_and_abuse#NETGEAR_and_the_University_of_Wisconsin.E2.80.93Madison
>
> It's one thing to come up with a solution that works for the 300 (total wild guess) people
> on this list. But to be useful for field deployable, it really needs to be able
> to handle a "every Comcast customer in a major metro area", because we *do*
> want this stuff to work well when this makes it into the CPE that Comcast
> gives every new customer, right? :)
the key thing here is to stagger the work.
Don't have every device do the test immediatly at startup. As you noted, that
will collapse as they all start up at once.
Have them operate from their saved stats and test at (largish) random offsets.
ideally, have this test be against an ANYCAST address, so that the ISP can run a
copy internally without having to reconfigure the clients.
David Lang
next prev parent reply other threads:[~2014-07-25 23:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-20 13:19 [Cerowrt-devel] " Rich Brown
2014-07-20 13:27 ` David P. Reed
2014-07-20 18:41 ` [Cerowrt-devel] SIMET: nationwide bw/latency/jitter test effort in Brazil Henrique de Moraes Holschuh
2014-07-23 5:36 ` [Cerowrt-devel] Check out www.speedof.me - no Flash Alex Elsayed
2014-07-25 9:10 ` [Cerowrt-devel] [Bloat] " Neil Davies
2014-07-25 12:09 ` Rich Brown
2014-07-25 12:24 ` Neil Davies
2014-07-25 14:17 ` Sebastian Moeller
2014-07-25 14:25 ` Martin Geddes
2014-07-25 15:58 ` Sebastian Moeller
2014-07-25 16:32 ` Martin Geddes
2014-07-25 17:12 ` Sebastian Moeller
2014-07-25 17:14 ` Neil Davies
2014-07-25 17:17 ` Sebastian Moeller
2014-07-25 17:29 ` Martin Geddes
2014-07-25 21:13 ` David Lang
2014-07-25 22:17 ` dpreed
2014-07-25 23:26 ` David Lang
2014-07-26 13:02 ` Sebastian Moeller
2014-07-26 20:53 ` David Lang
2014-07-26 22:00 ` Sebastian Moeller
2014-07-26 22:30 ` David Lang
2014-07-26 23:14 ` Sebastian Moeller
2014-07-26 20:16 ` Neil Davies
2014-07-25 14:27 ` Neil Davies
2014-07-25 16:02 ` Sebastian Moeller
2014-07-25 21:20 ` David Lang
2014-07-25 22:29 ` Valdis.Kletnieks
2014-07-25 23:30 ` David Lang [this message]
2014-07-26 12:53 ` Sebastian Moeller
2014-07-25 15:05 ` David P. Reed
2014-07-25 15:46 ` Rich Brown
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=alpine.DEB.2.02.1407251626490.21739@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=Valdis.Kletnieks@vt.edu \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=neil.davies@pnsol.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