From: Stephen John Smoogen <smooge@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Bloat] Two d-link products tested for bloat...
Date: Thu, 26 Feb 2015 09:56:42 -0700 [thread overview]
Message-ID: <CANnLRdhrDB=Dq+r6SEsm3vrQDsQ7npN9J2kg8z1pfoO=G-EhjA@mail.gmail.com> (raw)
In-Reply-To: <CAJq5cE0b7YiJ2R_J0D830hXbEctSOwK_2OdJOp+U4xNwSd_mnA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1504 bytes --]
On 25 February 2015 at 17:18, Jonathan Morton <chromatix99@gmail.com> wrote:
> > Here's a comparison plot of box totals:
> http://www.candelatech.com/downloads/rtt_fair4be-comparison-box-plot.png
>
> That's a real mess. All of them utterly fail to get download bandwidth
> anywhere near the upload (am I right in assuming it should ideally be about
> equal?), and the only ones with even halfway acceptable latency are the
> ones with least throughput in either direction.
>
Possibly. The two issues with wireless is that it is a hub like network and
that the system has to figure out a lot of noise (everthing from
microwaves, wireless phones to other AP's on the same or nearby frequencies
which intefere). Also depending on the antenae setup it is going to be both
sending and recieving from the same post which brings in other latencies.
Since most traffic is 'streaming' then the hardware is going to be oriented
on making download latencies the lowest and upload latencies not as much a
problem. If he gets the same profile on the wired side as the wireless side
then it is more of an indicator of software/hardware issues which might be
fixable. On the wireless side there is a TON of stuff you have to clean out
from any tests to make sure the results are 'valid' (to some degree of
valid).
> - Jonathan Morton
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
>
--
Stephen J Smoogen.
[-- Attachment #2: Type: text/html, Size: 2465 bytes --]
prev parent reply other threads:[~2015-02-26 16:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 2:04 Dave Taht
2015-02-20 5:32 ` Aaron Wood
2015-02-20 8:47 ` Jonathan Morton
2015-02-20 9:03 ` Dave Taht
2015-02-20 17:20 ` [Bloat] [Cerowrt-devel] " dpreed
2015-02-26 0:00 ` [Bloat] " Isaac Konikoff
2015-02-26 0:18 ` Jonathan Morton
2015-02-26 0:23 ` Dave Taht
2015-02-26 4:22 ` Isaac Konikoff
2015-02-26 4:37 ` Dave Taht
2015-02-27 5:00 ` Isaac Konikoff
2015-02-27 5:12 ` Dave Taht
2015-02-27 19:15 ` Isaac Konikoff
2015-02-26 16:56 ` Stephen John Smoogen [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/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='CANnLRdhrDB=Dq+r6SEsm3vrQDsQ7npN9J2kg8z1pfoO=G-EhjA@mail.gmail.com' \
--to=smooge@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=chromatix99@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