Historic archive of defunct list bloat-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Azin Neishaboori <azin.neishaboori@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: bloat-devel@lists.bufferbloat.net
Subject: Re: contradictory WiFi flent results
Date: Fri, 18 Jan 2019 03:05:55 -0500	[thread overview]
Message-ID: <CADXq5+_XEZy6Jic4m1rs0emsK2x60E1Nr2TQrQ6Wih50=6V=zQ@mail.gmail.com> (raw)
In-Reply-To: <9D460DD5-67CF-4D38-AEBC-2284AD4BCFC3@gmail.com>

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

Hi Jonathan
Thank you for your reply and insight. You are right about my setup.

Just wondering if you have some insight into why I get significantly better
download (not uplad) throughput by all other methods over cubic, including
bbr. I mean, bbr on the sender side would mean I am supposed to get
improvement on upload. Granted that my poor setup could distort any gains
on upload by bbr, why do I get throughput gains on download?

Thank you for your help
Best
Azin


On Fri, Jan 18, 2019 at 1:27 AM Jonathan Morton <chromatix99@gmail.com>
wrote:

> > On 18 Jan, 2019, at 6:25 am, Azin Neishaboori <
> azin.neishaboori@gmail.com> wrote:
> >
> > My setup is pretty simple. I am on WiFi on my PC, and run flent on an
> Ubuntu VM on a virtual machine, and connect to netperf.bufferbloat.net.
>
> From a technical point of view, that really isn't a "simple" setup.  The
> very fact that you're running Linux in a VM means it probably doesn't have
> direct control of the wifi hardware - rather, the host OS does, and I very
> much doubt that Windows is very intelligent about it.  Then your path
> involves an awful lot of Internet infrastructure on the way to the remote
> server and back.
>
> So your simple prioritised ack is the solution that works, because it's
> the only solution that actually does anything in your setup.
>
>  - Jonathan Morton
>
>

[-- Attachment #2: Type: text/html, Size: 1880 bytes --]

  reply	other threads:[~2019-01-18  8:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18  4:25 Azin Neishaboori
2019-01-18  6:27 ` Jonathan Morton
2019-01-18  8:05   ` Azin Neishaboori [this message]
2019-01-18  8:14     ` Jonathan Morton
     [not found] ` <CAC938Dj7P5JxyiPFar1NFqvJpd1hadNZwGgoMghfV-PUaRHp8g@mail.gmail.com>
2019-01-18  7:54   ` Azin Neishaboori

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADXq5+_XEZy6Jic4m1rs0emsK2x60E1Nr2TQrQ6Wih50=6V=zQ@mail.gmail.com' \
    --to=azin.neishaboori@gmail.com \
    --cc=bloat-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