Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: William Katsak <wkatsak@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Comcast Uplink Buffers
Date: Thu, 5 Mar 2015 07:43:32 -0800	[thread overview]
Message-ID: <CAA93jw7+MkoxfHiaMdNBgz8s6f8s0A+BZWFpkLhyjF9SrNY9vw@mail.gmail.com> (raw)
In-Reply-To: <54F877C5.3070300@gmail.com>

well, cerowrt's inbound shaper runs out of cpu at +60mbits. That is
possibly part of your problem.

the peaks you are seeing are not bad - but to me, probably indicative
of running out of cpu, which will among other things, drop packets
burstily.

As comcast has rolled out 100mbit+ service in a ton of places
(including my home), we really, really, really need to find a way to
do better rate shaping at higher speeds (or develop a faster policer)
on some successor hardware.

If you turn off inbound shaping (0 for that parameter) my measurements
typically show over 600ms of latency on inbound on comcast at 100mbit
down, but at least, doing the tcp_upload tests, we can hold the upload
more under control. It is a totally unsatisfactory thing to have
downloads got so much out of control, it really messes up other
things, inside of a few seconds, on big downloads, but at this point I
have to recommend turning off inbound shaping and just living with it.

Very high on my list now is finally writing (or tom sawyering someone
into writing!) "bobbie - the kinder, gentler policer" in the hope that
that could actually run faster and better than shaping does on this
low end hardware.



On Thu, Mar 5, 2015 at 7:35 AM, William Katsak <wkatsak@gmail.com> wrote:
> Hello all,
>
> I just moved and had to switch my ISP from Optimum (Cablevision) to Comcast
> (100/10 link).
>
> I am running my own port of simple.qos over to Debian/Ubuntu, and it worked
> fine on Cablevision (I basically use scripts in if-pre-up.d and
> if-post-down.d to set the variables set up/tear down simple.qos).
>
> However, since I moved over to Comcast, I am seeing something like 600 ms of
> uplink buffering according to Netlyzer. Also, the Internet browsing "feels"
> slow when Netflix is in use elsewhere in the apartment (like before I knew
> anything about bufferbloat).
>
> My config looks like this:
> UPLINK=7500
> DOWNLINK=85000
> QDISC=fq_codel
> LLAM="tc_stab"
> LINKLAYER="none"
> OVERHEAD=0
> STAB_MTU=2047
> STAB_MPU=0
> STAB_TSIZE=512
> AUTOFLOW=0
> LIMIT=1001   # sane global default for *LIMIT for fq_codel on a small memory
> device
> ILIMIT=
> ELIMIT=
> ITARGET="auto"
> ETARGET="auto"
> IECN="ECN"
> EECN="NOECN"
> SQUASH_DSCP="1"
> SQUASH_INGRESS="0"
> IQDISC_OPTS=""
> EQDISC_OPTS=""
> TC=`which tc`
> #TC="sqm_logger tc"# this redirects all tc calls into the log
> IP=$( which ip )
> INSMOD=`which modprobe`
> TARGET="5ms"
> IPT_MASK="0xff"
> IPT_MASK_STRING="/${IPT_MASK}"     # for set-mark
>
> I've also attached the output of a run of rrul against
> netperf.bufferbloat.net.
>
> Any insight?
>
> Thanks,
> Bill
>
>
> --
> ****************************************
> William Katsak <wkatsak@gmail.com>
> ****************************************
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>



-- 
Dave Täht
Let's make wifi fast, less jittery and reliable again!

https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb

  reply	other threads:[~2015-03-05 15:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05 15:35 William Katsak
2015-03-05 15:43 ` Dave Taht [this message]
2015-03-05 15:49   ` William Katsak
2015-03-05 19:05     ` Aaron Wood
2015-03-05 19:14       ` Dave Taht
2015-03-05 19:52       ` William Katsak

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/cerowrt-devel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=CAA93jw7+MkoxfHiaMdNBgz8s6f8s0A+BZWFpkLhyjF9SrNY9vw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=wkatsak@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