From: Juergen Botz <jurgen@botz.org>
To: Collin Anderson <cmawebsite@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] hardware suggestions?
Date: Wed, 28 Aug 2013 09:00:32 -0300 [thread overview]
Message-ID: <521DE660.5060602@botz.org> (raw)
In-Reply-To: <CAFO84S6YBHYVSyj3XLNchh5caRMPXe=q0R7zB_WPfbnvGEOt6Q@mail.gmail.com>
On 08/26/2013 09:44 PM, Collin Anderson wrote:
> After 5 years of knowingly suffering from high latency from uploads
> through Comcast, I have finally discovered the term "bufferbloat" and
> am glad to see that at least some people are pushing for better
> queuing algorithms. I use ssh all day for making websites at work and
> would like to eliminate, or at least reduce latency from buffer bloat.
This doesn't answer your question, but here's another way to improve
your life significantly: use "mosh" instead of bare-bones ssh. See
"http://mosh.mit.edu/", try it, and weep with joy and relief...
:j
next prev parent reply other threads:[~2013-08-28 12:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 0:44 Collin Anderson
2013-08-28 12:00 ` Juergen Botz [this message]
2013-08-28 18:44 ` Dave Taht
2013-08-29 13:18 ` Luke Hamburg
2013-08-30 18:17 ` Michael Richardson
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=521DE660.5060602@botz.org \
--to=jurgen@botz.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=cmawebsite@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