Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Aaron Wood <woody77@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Frank Horowitz <frank@horow.net>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] High Performance (SSH) Data Transfers using fq_codel?
Date: Thu, 13 Nov 2014 20:37:34 -0800	[thread overview]
Message-ID: <CALQXh-NAsimUOQmEJOPSLc9ETpPRaYCHuQ4oLntev3mOyD1GPA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7j1PMrxYm9nmx-7A7KwfyUymPFpFhgy5Xf1T1O_R4D8Q@mail.gmail.com>

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

I have a couple friends in that crowd, and they _also_ aren't using shared
lines.  So they don't worry in the slightest about congestion when they're
trying to keep dedicated links fully saturated.  They're big issue with
dropped packets is that some of the TCP congestion-control algorithms kick
in on a single dropped packet:
http://fasterdata.es.net/network-tuning/tcp-issues-explained/packet-loss/

I'm thinking that some forward-error-correction would make their lives
much, much better.

-Aaron

On Thu, Nov 13, 2014 at 7:11 PM, Dave Taht <dave.taht@gmail.com> wrote:

> One thing the HPC crowd has missed is that in their quest for big
> buffers for contenental distances, they hurt themselves on shorter
> ones...
>
> ... and also that big buffers with FQ on them works just fine in the
> general case.
>
> As always I recomend benchmarking - do a rrul test between the two
> points, for example, with their recomendations.
>
>
> On Fri, Oct 17, 2014 at 4:21 PM, Frank Horowitz <frank@horow.net> wrote:
> > G’Day folks,
> >
> > Long time lurker. I’ve been using Cero for my home router for quite a
> while now, with reasonable results (modulo bloody OSX wifi stuffola).
> >
> > I’m running into issues doing zfs send/receive over ssh across a
> (mostly) internet2 backbone between Cornell (where I work) and West
> Virginia University (where we have a collaborator on a DOE sponsored
> project. Both ends are linux machines running fq_codel configured like so:
> >         tc qdisc
> >         qdisc fq_codel 0: dev eth0 root refcnt 2 limit 10240p flows 1024
> quantum 1514 target 5.0ms interval 100.0ms ecn
> >
> > I stumbled across hpn-ssh <https://www.psc.edu/index.php/hpn-ssh> and
> —  of particular interest to this group — their page on tuning TCP
> parameters:
> >
> > <http://www.psc.edu/index.php/networking/641-tcp-tune>
> >
> > N.B. their advice to increase buffer size…
> >
> > I’m curious, what part (if any) of that advice survives with fq_codel
> running on both ends?
> >
> > Any advice from the experts here would be gratefully received!
> >
> > (And thanks for all of your collective and individual efforts!)
> >
> > Cheers,
> >         Frank Horowitz
> >
> >
> > _______________________________________________
> > Cerowrt-devel mailing list
> > Cerowrt-devel@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/cerowrt-devel
> >
>
>
>
> --
> Dave Täht
>
> thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>

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

  reply	other threads:[~2014-11-14  4:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-17 23:21 Frank Horowitz
2014-11-14  3:11 ` Dave Taht
2014-11-14  4:37   ` Aaron Wood [this message]
2014-11-14 14:45     ` David P. Reed
2014-11-15 22:47 ` Dave Taht

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=CALQXh-NAsimUOQmEJOPSLc9ETpPRaYCHuQ4oLntev3mOyD1GPA@mail.gmail.com \
    --to=woody77@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=frank@horow.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