From: John Klimek <jklimek@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] fq_codel settings for 25/3 connection?
Date: Tue, 16 Feb 2016 14:27:18 -0500 [thread overview]
Message-ID: <CC98C6CC-D95C-4B39-916D-CD8B5C509CC7@gmail.com> (raw)
In-Reply-To: <CAA93jw6d8A3L4D9oSBbF3OJSY5V1+f_oNWYrJJynvZ_heN+xEg@mail.gmail.com>
Thanks very much for the information! (I've been reading 20+ page threads on Ubiquity's forum looking for messages that you've posted)
I'm going to be testing an EdgeRouter X which doesn't support hardware acceleration so I don't think I have to worry about TCP offload (?). (I'd like to use my existing x86 hardware but I can't find a solid router OS that I like)
I'll also go ahead and enable fq_codel on my downstream and hope for the best.
Thanks again,
John
> On Feb 16, 2016, at 2:19 PM, Dave Taht <dave.taht@gmail.com> wrote:
>
>> 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
prev parent reply other threads:[~2016-02-16 19:27 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
2016-02-16 19:27 ` John Klimek [this message]
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=CC98C6CC-D95C-4B39-916D-CD8B5C509CC7@gmail.com \
--to=jklimek@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@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