From: Jaap Buurman <jaapbuurman@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>, chromatix99@gmail.com
Cc: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] Major Bufferbloat
Date: Mon, 27 Mar 2017 13:56:02 +0200 [thread overview]
Message-ID: <CAN-r--nwcLAkk0=+F_ZTNmXnUN=dhfRPbChiCa+T41Fx=MV4sw@mail.gmail.com> (raw)
In-Reply-To: <878tnraqn7.fsf@alrua-x1>
[-- Attachment #1: Type: text/plain, Size: 1500 bytes --]
Thank you very much for the quick replies! I tried two clients, one laptop
with the Intel 7265ac chipset (Just to be clear, these tests were done on
2.4ghz n). And another client with an Artheros chipset. I am not entirely
sure which one exactly, I can check in a few hours once I get home. Both
clients were showing the same behavior. The Intel chipset was using Windows
8.1, while the Artheros chipset was using Windows 10. As a sidenote, I will
try out Ubuntu clients as well once I get home.
I initially also suspected bloated clients. But both clients showed an A
bufferbloat score on an Archer C7 V2 2.4ghz wifi. This was the exact same
test as the one in the OP, so with 32 upload streams. Unfortunately, I do
not have the Archer anymore, so I cannot repeat the iperf tests.
On Mar 27, 2017 13:46, "Toke Høiland-Jørgensen" <toke@toke.dk> wrote:
> Jaap Buurman <jaapbuurman@gmail.com> writes:
>
> > Hello all,
> >
> > I'm seeing major bufferbloat issues on my 2.4ghz network that is run
> > on a DIR-860l B1, which uses the MT7602E chip. I am running the latest
> > stable LEDE. Strangely, I am only getting bufferbloat issues with a
> > high number of concurrent data streams from my wireless-n client to my
> > router. An extensive test showing the exact situation in which my
> > bufferbloat issues are occuring are found in the 7th post of the
> > following thread:
>
> What chipset/driver is the client running? Sounds like that is bloated?
>
> -Toke
>
[-- Attachment #2: Type: text/html, Size: 1915 bytes --]
next prev parent reply other threads:[~2017-03-27 11:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 11:41 Jaap Buurman
2017-03-27 11:45 ` Jonathan Morton
2017-03-27 11:46 ` Toke Høiland-Jørgensen
2017-03-27 11:56 ` Jaap Buurman [this message]
2017-03-27 12:21 ` Jonathan Morton
2017-03-27 13:41 ` Jaap Buurman
2017-03-27 14:25 ` marty
2017-03-27 14:54 ` marty
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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAN-r--nwcLAkk0=+F_ZTNmXnUN=dhfRPbChiCa+T41Fx=MV4sw@mail.gmail.com' \
--to=jaapbuurman@gmail.com \
--cc=chromatix99@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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