From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 903313B260 for ; Wed, 16 Nov 2016 15:28:02 -0500 (EST) Received: by mail-wm0-x229.google.com with SMTP id g23so264833383wme.1 for ; Wed, 16 Nov 2016 12:28:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=aEhoOadTkRZym1UngSP5m3/Si88PpRmyLTBKxm8vxJA=; b=Wo9I/pLiKAbJzGoR66hJ09U/kCAFNUKrDNdnDU5sXILiwMswdmtTYrlDldbRC6moZ5 qnVK5G5ur183iZUTm3vqNeO1fTIVFBATh/Fq/up1k9iC7x5+FSx5fsrYdM4kFmlUqli6 n31ZOLPpn+o4i+SQjwH44ncHjiv710R1su9AcxXVhNdLGXE7G/s1b8TWcCDouLo8p7Cq KyyQJi6S7Tj6GszKXBYGxChWcNhsOsJvHB+ZYbpFuRCz0gBPYbFUDYVXh7ns5Ta1Uba8 5tBAqbuxOAmxZYsTCQN4rZGWS3xArT13s70GCxBf9u0DNIV0lxXx6iUPtr8FUPM03Z8L qZTw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=aEhoOadTkRZym1UngSP5m3/Si88PpRmyLTBKxm8vxJA=; b=D6aINMAVTCZ/d+rYMGz36Mt82c7VvhOff32gmG4kTfTOos+MAV1/335kF8rcZAOsNJ EPNBrnSOp0UIv/2FmAOsfEwobSFud/j0NzVA0XFzVhM1Oc4/TPjvWv+GTI//mdb+WAms u+UEO+yS77MFA5q3iIvpmNYlHKrie0yf1smU/3u3Mp/92jwwHm4HSX9OTc2+skDiqkN2 IFb+V7gQC8q9daQRBc+8aucuLkdLuG1YxeaWFpeF2Hoh8GVB+S8Ry0X0gFIqOGhznkZa B8MshSo71BTt9m8c73ZKyI8n5fbMPe8d5bgTUnRo4ZPI0173tvgstPCvTZxsTVMEym32 KTOQ== X-Gm-Message-State: ABUngvdflekxtwNu5MSQZmCRu5mKL7kWsucYifVLQhe0IImGHVHla8YsDHoZjTq4/I0eGgxD4vNWfKS6OcsSWA== X-Received: by 10.194.127.40 with SMTP id nd8mr3770646wjb.43.1479328081535; Wed, 16 Nov 2016 12:28:01 -0800 (PST) MIME-Version: 1.0 Sender: justinbeech@gmail.com Received: by 10.28.135.198 with HTTP; Wed, 16 Nov 2016 12:27:20 -0800 (PST) In-Reply-To: <389eca46-80cf-99ae-9669-46e7fe767cbc@kau.se> References: <389eca46-80cf-99ae-9669-46e7fe767cbc@kau.se> From: jb Date: Thu, 17 Nov 2016 07:27:20 +1100 X-Google-Sender-Auth: OG--fkNS9z18hsgOZ1zoqNTDz18 Message-ID: To: Stefan Alfredsson Cc: David Lang , bloat Content-Type: multipart/alternative; boundary=e89a8f83a763ce708a054170e84f Subject: Re: [Bloat] bufferbloat at high edge rates X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2016 20:28:02 -0000 --e89a8f83a763ce708a054170e84f Content-Type: text/plain; charset=UTF-8 Hi Stefan, The reason for the higher latency is the auto-selection of the servers, the IP address you were on for the browser tests was for a reason I can't yet work out, only offering US servers. It is surprising that you got a gigabit, pretty much. You can avoid this problem in the browser test by selecting manually, using test preferences, only euro servers and it will use the nearest of those. The command line test was pinging all 76 servers so it used euro ones. So my reaction from your tests is that the in-brwser buffer bloat testing is probably accurate even at high speeds and with the same servers, probably returning the same measurement. thanks -Justin On Wed, Nov 16, 2016 at 5:00 PM, Stefan Alfredsson wrote: > 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/spee > dtest/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>> 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 >> >> >> >> This does not seem to be reporting any bloat info (I've run it a >> couple times) >> >> http://www.dslreports.com/speedtest/6156013 >> >> >> David Lang >> _______________________________________________ >> Bloat mailing list >> Bloat@lists.bufferbloat.net >> https://lists.bufferbloat.net/listinfo/bloat >> >> >> >> >> >> _______________________________________________ >> Bloat mailing list >> Bloat@lists.bufferbloat.net >> https://lists.bufferbloat.net/listinfo/bloat >> > > > > --e89a8f83a763ce708a054170e84f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Stefan,=C2=A0

The reason for the higher la= tency is the auto-selection of the servers, the IP address you were on for = the browser tests was for a reason I can't yet work out, only offering = US servers. It is surprising that you got a gigabit, pretty much.

You can avoid this problem in the browser test by selecting= manually, using test preferences, only euro servers and it will use the ne= arest of those.=C2=A0

The command line test was pi= nging all 76 servers so it used euro ones.

So my r= eaction from your tests is that the in-brwser buffer bloat testing is proba= bly accurate even at high speeds and with the same servers, probably return= ing the same measurement.

thanks
-Justin=

On Wed, Nov 16, 2016 at 5:00 PM, Stefan Alfredsson <<= a href=3D"mailto:stefan.alfredsson@kau.se" target=3D"_blank">stefan.alfreds= son@kau.se> wrote:
I had th= e 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 t= he 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=C2=A0 (~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 deskto= p.

- CLI tests were run in a docker container, for security purposes. I used h= ost 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 /t= mp 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 inst= ead 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 b= loat.

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 is= n't doing any buffer bloat testing.

I'm not sure that is the issue but that's the first thing that come= s to mind..


On Wed, Nov 16, 2016 at 11:34 AM, David Lang <david@lang.hm <mailto:david@lang.hm>> wrote:

=C2=A0 =C2=A0 On Tue, 15 Nov 2016, jb wrote:

=C2=A0 =C2=A0 =C2=A0 =C2=A0 The command line tool is available to anyone no= w (Windows, OSX
=C2=A0 =C2=A0 =C2=A0 =C2=A0 and linux),
=C2=A0 =C2=A0 =C2=A0 =C2=A0 it does buffer bloat probing, using ICMP if run= as root, and
=C2=A0 =C2=A0 =C2=A0 =C2=A0 is immune to
=C2=A0 =C2=A0 =C2=A0 =C2=A0 any browser issues. It can be downloaded here f= rom the sticky:
=C2=A0 =C2=A0 =C2=A0 =C2=A0 http://www.dslreports.com= /forum/speedtestbinary
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <http://www.dslreports= .com/forum/speedtestbinary>


=C2=A0 =C2=A0 This does not seem to be reporting any bloat info (I've r= un it a
=C2=A0 =C2=A0 couple times)

=C2=A0 =C2=A0 http://www.dslreports.com/speedtest/= 6156013
=C2=A0 =C2=A0 <http://www.dslreports.com/speedtes= t/6156013>

=C2=A0 =C2=A0 David Lang
=C2=A0 =C2=A0 _______________________________________________
=C2=A0 =C2=A0 Bloat mailing list
=C2=A0 =C2=A0 Bloat@lists.bufferbloat.net <mailto:Bloat@lists.bufferbloat.net&g= t;
=C2=A0 =C2=A0 https://lists.bufferbloat.net/listin= fo/bloat
=C2=A0 =C2=A0 <https://lists.bufferbloat.net/lis= tinfo/bloat>




_______________________________________________
Bloat mailing list
Bloat@list= s.bufferbloat.net
https://lists.bufferbloat.net/listinfo/bloat




--e89a8f83a763ce708a054170e84f--