General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Stefan Alfredsson <Stefan.Alfredsson@kau.se>
To: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] AQM and PPP on Linux
Date: Wed, 29 Jul 2015 15:15:42 +0200	[thread overview]
Message-ID: <20150729131542.GA16305@sa-pc> (raw)
In-Reply-To: <CAA93jw6XbCiA6Apew-qxdmt1fzAo2kX2dw2Uf_W-idL7bX5C1w@mail.gmail.com>

* Quoting Dave Taht <dave.taht@gmail.com> [28 Jul-15 16:44]:
> On Tue, Jul 28, 2015 at 3:09 PM, Juliusz Chroboczek
> <jch@pps.univ-paris-diderot.fr> wrote:
> > I'm currently away from home, and using a 3G modem for Internet access.
> > I've found out that both NetworkManager and wvdial/pppd setup the
> > interface to use pfifo_fast (with a qlen of a mere 3 packets!).  Setting
> > fq_codel manually appears to work fine, but needs to be redone every time
> > the modem has a hiccup.
> 
> However, the netusb-related drivers, and the 3g devices themselves,
> contain oft-huge buffers that reduce the effectiveness of any aqm or
> fq system, sometimes to immeasurability.
> 
> I would be very interested in flent benchmarks of your 3g device with
> the 3 packet txqueue and with fq_codel, for the tcp_upload, rrul, and
> rrul_be tests.


I have a station with mobile broadband USB modems (4xHuawei E392),
directly connected to a Linux box running kernel 3.16.3, with
a (non-public) netperf server (same kernel) hosted on the well-connected
Swedish university network.

I also have a 3 packet txqueue, and ran the flent tcp_upload, rrul, rrul_be
for 3.5G (HSPA+) and 4G (LTE) networks for one of the operators/modems.
For comparison, I ran both pfifo_fast and fq_codel.

The execution script, output and flent result files are available at
https://www.dropbox.com/s/n5tc1dhtu9jdplz/bloatlist-ppp-150729.zip

From flent --gui inspections, I'd say there is about a factor 10 increase
from base to load latency (from around 40-50 ms to around 400-500 ms),
for both pfifo_fast and fq_codel, for both link types,
with some transients above 1000 ms.


Juliusz: Regarding data usage, the 4G measurements consumed 1.4 Gbyte
download and 357 Mbyte upload - but it all depends on the network
throughput as the experiments are time bound (by default 60 seconds).
For 3.5G 100 Mbyte data was sent, and guesstimately 500 Mbyte received
(sorry, didn't capture the amount; but it can probably be found in
the trace files if necessary. However it all depends on your link 
throughput which will be different from mine anyway).


Cheers,
 Stefan

-- 
Stefan Alfredsson, PhD         Tel: +46 (0) 54 700 1668
Datavetenskap                  Kontor: 21E-414 (Hus Vanern)
Karlstads universitet          PGP 0xB19B4B16
SE-651 88 Karlstad             http://www.cs.kau.se/stefalfr/

  parent reply	other threads:[~2015-07-29 13:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28 13:09 Juliusz Chroboczek
2015-07-28 13:33 ` Toke Høiland-Jørgensen
2015-07-28 13:50   ` Juliusz Chroboczek
2015-07-28 14:05     ` Toke Høiland-Jørgensen
2015-07-28 14:11       ` Simon Barber
2015-07-28 14:21         ` Eric Dumazet
2015-07-28 14:31           ` Simon Barber
2015-07-28 14:43             ` Jonathan Morton
2015-07-28 14:49             ` Eric Dumazet
2015-07-28 14:55               ` Eric Dumazet
2015-07-28 16:02               ` Alan Jenkins
2015-07-28 16:22             ` Sebastian Moeller
2015-07-28 17:11               ` Michael Welzl
2015-07-29  7:19         ` David Lang
2015-07-28 19:20       ` Juliusz Chroboczek
2015-07-28 19:29         ` Alan Jenkins
2015-07-28 14:18     ` Eric Dumazet
2015-07-28 14:44 ` Dave Taht
2015-07-28 14:52   ` Eric Dumazet
2015-07-28 19:24   ` Juliusz Chroboczek
2015-07-28 19:31     ` Bill Ver Steeg (versteb)
2015-07-28 20:10     ` Alan Jenkins
2015-07-28 20:45       ` Alan Jenkins
2015-07-29 13:15   ` Stefan Alfredsson [this message]
2015-07-29 13:41     ` Dave Taht

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=20150729131542.GA16305@sa-pc \
    --to=stefan.alfredsson@kau.se \
    --cc=bloat@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