From: Hal Murray <hmurray@megapathdsl.net>
To: bloat@lists.bufferbloat.net
Cc: Hal Murray <hmurray@megapathdsl.net>
Subject: [Bloat] came across an unexpected side-effect of bufferblo
Date: Mon, 03 Aug 2015 12:45:42 -0700 [thread overview]
Message-ID: <20150803194542.A6AF4406057@ip-64-139-1-69.sjc.megapath.net> (raw)
> Amazon support forums that said after 3 hours of uploading to Amazon, their
> cable modem would crash and reboot. The reason was that the SNMP the cable
> modem needed to stay healthy was timing out (due to the excessive latency
> induced by the continuous uploading). The author didn't know it was
> bufferbloat, of course.
> I thought that was an interesting little result of never testing "full
> speed" for long periods of time.
I had a similar bug in my code many many many years ago.
The context was a TCP connection feeding a Versatec plotter. (Remember
them?) Somebody was making a banner for his daughters volleyball team. He
turned the text sideways and set the font size to 3 feet tall. It took the
printer a long time to process a few characters of text. Some timer didn't
handle that case. The fix was only one line.
------
Does anybody have a checklist of things like that to test?
--
These are my opinions. I hate spam.
reply other threads:[~2015-08-03 19:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150803194542.A6AF4406057@ip-64-139-1-69.sjc.megapath.net \
--to=hmurray@megapathdsl.net \
--cc=bloat@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