From: Stefan Alfredsson <stefan.alfredsson@kau.se>
To: jb <justin@dslr.net>, David Lang <david@lang.hm>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] bufferbloat at high edge rates
Date: Wed, 16 Nov 2016 07:00:16 +0100 [thread overview]
Message-ID: <389eca46-80cf-99ae-9669-46e7fe767cbc@kau.se> (raw)
In-Reply-To: <CAH3Ss948=ceqbbEVbC-dJ+ZjhXgwXsaFPzBuepy8BYZxA7YW0w@mail.gmail.com>
I had the same problem, getting no bloat report. I tested just now
running as root, and got bloat measurements in
http://www.dslreports.com/speedtest/6166098 and
http://www.dslreports.com/speedtest/6166295
From Firefox, I get somewhat higer latency (~100 ms) versus ~20-60 ms
via the command line client:
http://www.dslreports.com/speedtest/6130740
http://www.dslreports.com/speedtest/6130727
http://www.dslreports.com/speedtest/6130708
http://www.dslreports.com/speedtest/6130690
Two things to note:
- Firefox tests were run yesterday at around lunchtime (~12.00 CET),
and CLI tests just now (~06.40 CET). So time-of-day effect may be a
reason for less bloat now. I'll do a better comparison when I get to my
desktop.
- CLI tests were run in a docker container, for security purposes. I
used host networking so it should not have affected measurements much,
but still. This was how it was executed:
// downloaded the dslreports cli tool to my host /tmp directory, mapping
/tmp to /host in the debian container
$ docker run --rm -t -i -v /tmp:/host:ro debian
root@db0ea060caa7:/# apt-get update ; apt-get install ca-certificates
[... snip ...]
root@db0ea060caa7:/# /host/dslrcli-linux-amd64
Selecting nearest servers....
Download Testing.....
Upload Testing.....
Uploading results...
Download : 883.56 Megabit/sec Upload : 895.32 Megabit/sec
http://www.dslreports.com/speedtest/6166098
A better option would be using CAP_NET_RAW, I'll see if this works
instead of running with full root privs.
/Stefan
On 16/11/16 05:09, jb wrote:
> It has to run as root / Admin in order to do ICMP in order to test
> buffer bloat.
>
> If you run it under a non privileged user account it cannot get
> permission for ICMP, so although it locates the nearest servers using
> http ping, it isn't doing any buffer bloat testing.
>
> I'm not sure that is the issue but that's the first thing that comes
> to mind..
>
>
> On Wed, Nov 16, 2016 at 11:34 AM, David Lang <david@lang.hm
> <mailto:david@lang.hm>> wrote:
>
> On Tue, 15 Nov 2016, jb wrote:
>
> The command line tool is available to anyone now (Windows, OSX
> and linux),
> it does buffer bloat probing, using ICMP if run as root, and
> is immune to
> any browser issues. It can be downloaded here from the sticky:
> http://www.dslreports.com/forum/speedtestbinary
> <http://www.dslreports.com/forum/speedtestbinary>
>
>
> This does not seem to be reporting any bloat info (I've run it a
> couple times)
>
> http://www.dslreports.com/speedtest/6156013
> <http://www.dslreports.com/speedtest/6156013>
>
> David Lang
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net <mailto:Bloat@lists.bufferbloat.net>
> https://lists.bufferbloat.net/listinfo/bloat
> <https://lists.bufferbloat.net/listinfo/bloat>
>
>
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2016-11-16 6:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 19:02 Dave Taht
2016-11-14 20:06 ` Kathleen Nichols
2016-11-15 16:22 ` Dave Taht
2016-11-15 23:16 ` jb
2016-11-15 0:11 ` jb
2016-11-15 0:31 ` Dave Taht
2016-11-15 0:36 ` Jonathan Morton
2016-11-15 15:23 ` James Cloos
2016-11-15 15:43 ` Jan Ceuleers
2016-11-16 0:34 ` David Lang
2016-11-16 4:09 ` jb
2016-11-16 6:00 ` Stefan Alfredsson [this message]
2016-11-16 11:26 ` Stefan Alfredsson
2016-11-16 20:27 ` jb
2016-11-16 6:02 ` David Lang
[not found] ` <CY4PR04MB05665A2EFEB8CE55866C839A95BE0@CY4PR04MB0566.namprd04.prod.outlook.com>
2016-11-17 0:16 ` jb
2016-11-17 7:50 ` David Lang
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=389eca46-80cf-99ae-9669-46e7fe767cbc@kau.se \
--to=stefan.alfredsson@kau.se \
--cc=bloat@lists.bufferbloat.net \
--cc=david@lang.hm \
--cc=justin@dslr.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