Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Frank Horowitz <frank@horow.net>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] High Performance (SSH) Data Transfers using fq_codel?
Date: Fri, 17 Oct 2014 23:21:42 -0000	[thread overview]
Message-ID: <C1928D9C-5D30-438A-A63F-0B4CDDC72E4A@horow.net> (raw)

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

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


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 841 bytes --]

             reply	other threads:[~2014-10-17 23:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-17 23:21 Frank Horowitz [this message]
2014-11-14  3:11 ` Dave Taht
2014-11-14  4:37   ` Aaron Wood
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=C1928D9C-5D30-438A-A63F-0B4CDDC72E4A@horow.net \
    --to=frank@horow.net \
    --cc=cerowrt-devel@lists.bufferbloat.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