General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: John Klimek <jklimek@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] fq_codel settings for 25/3 connection?
Date: Tue, 16 Feb 2016 11:19:59 -0800	[thread overview]
Message-ID: <CAA93jw6d8A3L4D9oSBbF3OJSY5V1+f_oNWYrJJynvZ_heN+xEg@mail.gmail.com> (raw)
In-Reply-To: <86929A3A-5095-4506-8897-03EA5DABAF90@gmail.com>

On Tue, Feb 16, 2016 at 10:06 AM, John Klimek <jklimek@gmail.com> wrote:
> Does anybody have any suggested quantum/target values for a cable modem connection of 25/3?  (25 Mbps down, 3 Mbps up)

I would use a quantum 300 for the up. There is no need to fiddle with
the target values below 2.5mbits.

The edgerouter has issues with tcp offloads enabled. If you are not
using the other ports as routed ports, you can disable gro offloads on
all ports for lower latency at a huge cost in local bandwidth (this is
something that cake will fix if we can get ubnt to ship it one day.
http://www.bufferbloat.net/projects/codel/wiki/CakeTechnical )


>
> It looks like the defaults for Ubiquity EdgeRouter should work but I'm not sure if I can achieve better performance by tuning anything?

Make a change, measure with a good benchmark like flent's rrul test.

> Also, should I enable fq_codel on my downstream or only my upstream?

Both are severely overbuffered on cablemodems and CMTSes running at this speed.

http://burntchrome.blogspot.com/2014/05/fixing-bufferbloat-on-comcasts-blast.html

https://wiki.openwrt.org/doc/howto/sqm


> Thanks!
>
> - John
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat

  parent reply	other threads:[~2016-02-16 19:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16 18:06 John Klimek
2016-02-16 18:08 ` Rosen Penev
2016-02-16 19:19 ` Dave Taht [this message]
2016-02-16 19:27   ` John Klimek

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=CAA93jw6d8A3L4D9oSBbF3OJSY5V1+f_oNWYrJJynvZ_heN+xEg@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=jklimek@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