From: Isaac Konikoff <konikofi@candelatech.com>
To: Jonathan Morton <chromatix99@gmail.com>, Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Remy: Computer-Generated Congestion Control
Date: Thu, 21 Aug 2014 13:57:20 -0700 [thread overview]
Message-ID: <53F65D30.5050802@candelatech.com> (raw)
In-Reply-To: <CAJq5cE24_SRg7N_owKJ9bdcnvUqL5vGFm-RSY0WHi5eKB0FXsg@mail.gmail.com>
We regularly test out our WiFi Traffic Generator against a slew of
commercially available APs: Netgear, Cisco, Asus, Dlink...etc..
For 802.11a/b/g/n we have a 1200 station emulator:
http://candelatech.com/ct525-1200-6n_product.php
For 802.11ac we have a 384 station emulator:
http://candelatech.com/ct525-384-6ac_product.php
And we have various combinations of the above:
http://candelatech.com/lf_systems.php#wifire
Here are some sample capacity reports against a few different APs:
http://candelatech.com/downloads/wifi-capacity-reports-08152014.tar.gz
Isaac
On 08/21/2014 10:33 AM, Jonathan Morton wrote:
> I don't suppose anyone has set up a lab containing several hundred
> wireless clients and a number of APs? A stepping stone towards that
> would be a railway carriage simulator, with one AP, a simulated 3G
> uplink, and a couple of dozen clients.
>
> I wonder how well simply putting fq on each of the clients and fq_codel
> on the APs would work. My general impression is that fq is the right
> default choice for end hosts (which are generally not at the bottleneck)
> and fq_codel is the right default choice for bottleneck routers. A
> typical consumer router/AP might see the bottleneck for both directions,
> though not necessarily at the same time.
>
> - Jonathan Morton
>
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
--
Isaac Konikoff
Candela Technologies
konikofi@candelatech.com
Office: +1 360 380 1618
Cell: +1 360 389 2453
Fax: +1 360 380 1431
next prev parent reply other threads:[~2014-08-21 20:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 12:44 Baptiste Jonglez
2014-08-04 14:55 ` Dave Taht
2014-08-21 10:21 ` Michael Welzl
2014-08-21 17:04 ` Dave Taht
2014-08-21 17:33 ` Jonathan Morton
2014-08-21 19:50 ` Tim Upthegrove
2014-08-21 19:50 ` Alex Burr
2014-08-21 20:57 ` Isaac Konikoff [this message]
2014-08-21 19:46 ` Michael Welzl
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=53F65D30.5050802@candelatech.com \
--to=konikofi@candelatech.com \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--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