Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Pete Heist <pete@heistp.net>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Dave Taht <dave.taht@gmail.com>,
	Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] emulating wifi better - coupling qdiscs in netem?
Date: Mon, 18 Jun 2018 11:24:24 +0200	[thread overview]
Message-ID: <5CC11C44-6C78-410D-B699-B4B1A6F5FBDD@heistp.net> (raw)
In-Reply-To: <CAJq5cE2yfHM-mcAvEYM5nEnhEmno+pJhbhiXJN02sQ0Kyk4qig@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]


> On Jun 17, 2018, at 8:47 PM, Jonathan Morton <chromatix99@gmail.com> wrote:
> If you have instructions for setting up a test, I could try it.
> 

Ok, thanks for that, code and scripts are attached, see README.txt.

I now use plain netns (no lxc containers), which is easier to set up and has lower RTTs and higher throughputs, probably due to no bridge device.

Per Eric’s tip, the nfq no-op code is run with chrt -rr 99, which reduces RTTs somewhat and increases throughputs ~2-3x. No busy polling yet.

I also tried it on VMWare with a 2011 MBP, which looks radically better than the APU2 (for nfq, RTTs ~16% of APU2 and throughput 4x higher in the non-GSO case, 11x with GSO). Results attached, and to summarize:

ping mean (min-max) RTTs:

APU2, no nfq: 35 us (23-291)
APU2, nfq without GSO: 80 us (53-288)
APU2, nfq with GSO: 85 us (56-270)
2011 MBP, no nfq: 4 us (4-529) [11% of APU2]
2011 MBP, nfq without GSO: 13 us (11-197) [16% of APU2]
2011 MBP, nfq with GSO: 14 us (11-1568) [16% of APU2]

iperf3 throughputs (Gbps):

APU2, no nfq: 5.01 Gbps
APU2, nfq without GSO: 391 Mbps
APU2, nfq with GSO: 3.35 Gbps
2011 MBP, no nfq: 39.8 Gbps [7.9x APU2]
2011 MBP, nfq without GSO: 1.48 Gbps [3.8x APU2]
2011 MBP, nfq with GSO: 38.0 Gbps [11.3x APU2]

Results from a decent physical box instead of a VM may be interesting to see.

[-- Attachment #2.1: Type: text/html, Size: 2466 bytes --]

[-- Attachment #2.2: nfqtest.tar.gz --]
[-- Type: application/x-gzip, Size: 5226 bytes --]

[-- Attachment #2.3: Type: text/html, Size: 233 bytes --]

  reply	other threads:[~2018-06-18  9:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30 17:28 Dave Taht
2018-05-30 18:32 ` Bob McMahon
2018-05-30 18:54   ` Dave Taht
2018-05-30 18:58     ` Jonathan Morton
2018-05-30 19:19     ` Bob McMahon
2018-05-30 23:26       ` Dave Taht
2018-05-30 22:57 ` dpreed
2018-06-15 22:30   ` Dave Taht
2018-06-16 22:53     ` Pete Heist
2018-06-17 11:19       ` Jesper Dangaard Brouer
2018-06-17 15:16         ` Pete Heist
2018-06-17 16:09           ` Dave Taht
2018-06-17 18:38             ` Pete Heist
2018-06-17 18:47               ` Jonathan Morton
2018-06-18  9:24                 ` Pete Heist [this message]
2018-06-18 16:08                   ` Eric Dumazet
2018-06-18 19:33                     ` Pete Heist
2018-06-18 19:44                       ` Dave Taht
2018-06-18 21:54                         ` Pete Heist
2018-06-18 22:27                           ` Eric Dumazet
2018-06-17 20:42               ` Dave Taht
2018-06-18  1:02                 ` Eric Dumazet
2018-06-18  0:59       ` Eric Dumazet

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=5CC11C44-6C78-410D-B699-B4B1A6F5FBDD@heistp.net \
    --to=pete@heistp.net \
    --cc=chromatix99@gmail.com \
    --cc=dave.taht@gmail.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    /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