General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Forums1000 <forums1000@gmail.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] I am unable to pinpoint the source of bufferbloat
Date: Sat, 9 Feb 2013 18:27:14 +0100	[thread overview]
Message-ID: <CANfPCkVs5GY89YWphmJkz63Tqv8ts214po32_eGzmV49X2a7sA@mail.gmail.com> (raw)
In-Reply-To: <CANfPCkUesuUA4wMstNYJ-ehNXyWaCRG49Mw7HevnffR_Ed0a6A@mail.gmail.com>

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

Hi Jonathan and Dave

My entire LAN-network is gigabit. My cable subscription is 60 megabit down
and 4 megabit up.
Now, both my routers' WAN-port and the cable modems' LAN port are also
gigabit. The router can route LAN to WAN and the other way around (with NAT
and connection tracking enabled) in excess of 100 megabit.

Now my cable modem is a Motorola Surfboard SV6120E and hers is a Motorola
Surfboard CV6181E. My upload lag is 550ms and hers is only 220ms. Moreover,
at her place there are Powerplugs in the path limiting her download to 30
megabit instead of 60 megabit. Yet, the upload lag is much lower than mine.
There, it also did not matter where I ran Natalyzr, the result was always
220ms of bufferbload.

Could this still be only the modem?


On Sat, Feb 9, 2013 at 10:52 AM, Forums1000 <forums1000@gmail.com> wrote:

> Hi everyone,
>
> Can anyone give some tips on how to diagnose the sources of bufferbloat?
> According to the Netalyzr test at http://netalyzr.icsi.berkeley.edu/, I
> have 550ms of upload bufferbloat. I tried all kinds of stuff on my Windows
> 7 laptop:
>
> - For the Intel(R) 82567LF Gigabit Network Connection, I put receive and
> transmit buffers to the lowest value of 80 (80 bytes? 80 packets? I don't
> know). I also disabled interrupt moderation.
> Result? Still 550ms.
> - Then I connected my laptop directly to my cable modem, bypassing my
> Mikrotik 450G router. Result? Still 550ms of bufferbloat.
> - Then I put a 100 megabit switch between the cable modem an the laptop
> (as both cable modem and Intel NIC are gigabit). Result? Still 550ms of
> upload bufferbloat.
>
> I'm out of ideas now. It seems I can't do anything at all to lower
> bufferbloat. Or the Netalyzr test is broken?:-)
>
> many thanks for your advice,
> Jeroen
>
>

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

  parent reply	other threads:[~2013-02-09 17:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-09  9:52 Forums1000
2013-02-09 14:33 ` Jonathan Morton
2013-02-09 16:34 ` Dave Taht
2013-02-09 17:27 ` Forums1000 [this message]
2013-02-09 18:15   ` Jonathan Morton
2013-02-09 18:32     ` Forums1000
2013-02-09 19:10     ` this_is_not_my_name nor_is_this
2013-02-09 19:58       ` Dave Taht
     [not found]         ` <CANfPCkVSDxMF95rxd65WvX3EnN8DZ2=os+GE6wGgntE0bkvy=A@mail.gmail.com>
2013-02-09 22:06           ` Forums1000
2013-02-09 22:36             ` Dave Taht
2013-02-10 16:42               ` Forums1000
2013-02-10 16:55                 ` Jonathan Morton
2013-02-09 18:48 ` this_is_not_my_name nor_is_this
2013-02-09 19:07   ` Forums1000

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=CANfPCkVs5GY89YWphmJkz63Tqv8ts214po32_eGzmV49X2a7sA@mail.gmail.com \
    --to=forums1000@gmail.com \
    --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