From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ip-64-139-1-69.sjc.megapath.net (ip-64-139-1-69.sjc.megapath.net [64.139.1.69]) by huchra.bufferbloat.net (Postfix) with ESMTP id 4860E21F8D4 for ; Mon, 3 Aug 2015 12:45:45 -0700 (PDT) Received: from shuksan (localhost [127.0.0.1]) by ip-64-139-1-69.sjc.megapath.net (Postfix) with ESMTP id A6AF4406057; Mon, 3 Aug 2015 12:45:42 -0700 (PDT) X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3 To: bloat@lists.bufferbloat.net From: Hal Murray Date: Mon, 03 Aug 2015 12:45:42 -0700 Message-Id: <20150803194542.A6AF4406057@ip-64-139-1-69.sjc.megapath.net> Cc: Hal Murray Subject: [Bloat] came across an unexpected side-effect of bufferblo X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Aug 2015 19:46:14 -0000 > 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.