Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] CeroWRT and "FTTN" 50/10 VDSL2 (aka "FIBE")
Date: Mon, 30 Jun 2014 11:35:07 -0400	[thread overview]
Message-ID: <25681.1404142507@sandelman.ca> (raw)
In-Reply-To: <CAA93jw4Wr458KCTtpE1cUkr8vwQg4sesW0yPBS1a0exg=TdWtw@mail.gmail.com>


Dave Taht <dave.taht@gmail.com> wrote:
    > On Fri, Jun 27, 2014 at 12:37 PM, Dave Taht <dave.taht@gmail.com> wrote:
    >> On Tue, Jun 24, 2014 at 3:48 PM, Michael Richardson <mcr@sandelman.ca> wrote:
    >>>
    >>> On Monday I had VDSL2 installed at my home office.
    >>>
    >>> 50Mb/s down, 10Mb/s up from storm.ca. Native IPv6, but as far as I can tell,
    >>> they aren't speaking DHCPv6; anyway I kept my /56 from my previous
    >>
    >> Cool. I note that the wndr3800 runs out of horsepower at about 50mbit/10.

    > And when I say that, I mean it. HTB eats all the cpu, leaving nothing
    > for wifi , wifi crypto, the web interface, etc, at these rates. I have
    > long been looking for something more efficient than htb without much
    > luck.

Right now, with it still set at 50000, I see 49.86Mb/s from my ISPs' speedtest.storm.ca.
I'll take your advice and turn off download policing.

    > So assuming your downstream bloat isn't "bad", and you stick with cero
    > on this interface, I'd disable the downstream rate limiter entirely
    > (set it to 0), and just use sqm on the upstream. It is increasingly
    > hard to hit the higher bandwidth limits with normal traffic.

    > (but I'd love a rrul measurement all the same... )

I'll try to get it setup.... anecdotally, my ssh is really fast all the time.
I spend a lot of time ssh'ed into my SOHO desktop from my office, running
emacsclient in "-nw" mode.  In the pre-CODEL days, this resulted regularly in
me getting 20-40seconds ahead of the screen updates.  Post cerowrt/CODEL,
there were occasional periods of time when codel couldn't protected my typing
SSH from the ssh that was running sshfs/rsync.
(sshfs/rsync needs to invoke ssh with some option to make it apply DSCP to
the packets)

I'm think that with 10Mb/s up, I just won't care :-)

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


  reply	other threads:[~2014-06-30 15:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24 22:48 Michael Richardson
2014-06-27 19:37 ` Dave Taht
2014-06-27 20:15   ` Dave Taht
2014-06-30 15:35     ` Michael Richardson [this message]
2014-06-30 15:59       ` Dave Taht
2014-06-29  8:33   ` Baptiste Jonglez
2014-06-29 14:00     ` dpreed
2014-06-30 13:24   ` Michael Richardson
2014-06-30 13:55     ` Sebastian Moeller
2014-06-30 15:37       ` Michael Richardson
2014-06-30 19:17         ` Sebastian Moeller
2014-07-02 20:45           ` Michael Richardson
2014-07-03  9:39             ` Sebastian Moeller

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=25681.1404142507@sandelman.ca \
    --to=mcr@sandelman.ca \
    --cc=cerowrt-devel@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