From: Sebastian Moeller <moeller0@gmx.de>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] how's everybody's uptime?
Date: Fri, 6 Feb 2015 12:04:33 +0100 [thread overview]
Message-ID: <0556A811-405E-4FA2-B6F5-35DD1E108A87@gmx.de> (raw)
In-Reply-To: <B53DA6A3-EFD4-4C72-B1C4-3D4D1EECD7A3@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1612 bytes --]
On Sep 28, 2014, at 11:45 , Sebastian Moeller <moeller0@gmx.de> wrote:
[…]
>
>
> Now, I have performed a few netperf-wrapper tests recently and it seems there is something in my system that screws up latency under load roughly every minute (see attached image). Until recemty I believed these to be caused by my MacBooks wireless access, but the attached image is from a test win se00 (also no soft-irq spikes visible on top running on cerowrt). I begin to wonder whether these might be caused by ohcpd’s repeated search for a useable IPv6 link, but I digress.
>
>
>
This is not going to be too interesting, but for some closure I want to document the information about this issue (especially since cerowrt is completely innocent, and I want to avoid spoiling its reputation with another device’s issues)
So I figured that one out; it was the 2.4GHz wifi on my ISP’s modem-router (speed port w723v type A, avoid if possible); which was a) running without associated stations as an emergency fallback in case I screwed up cerowrt, and b) was actually wedging itself hard after 1 to 48 hours of operation in that it did not allow any station to connect. And in the wedged state it completely wiped out this modem-router’s wan throughput. Since this router was shared between my wired and wireless tests (after all this is the device talking DSL ;) ) it affected all my tests. Since I disabled that devices WLAN completely, the latency spikes are gone (actually now I have periodic spikes, but these are of much smaller magnitude and much less urgent to solve).\\\
Best Regards
Sebastian
[-- Attachment #2.1: Type: text/html, Size: 2315 bytes --]
[-- Attachment #2.2: latency_spikes_roughly_every_60sec.png --]
[-- Type: image/png, Size: 23046 bytes --]
next prev parent reply other threads:[~2015-02-06 11:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-27 17:23 Dave Taht
2014-09-27 17:47 ` Aaron Wood
2014-09-27 17:51 ` Jim Gettys
2014-09-27 18:01 ` Valdis.Kletnieks
2014-09-28 0:51 ` Rich Brown
2014-09-28 1:01 ` William Katsak
2014-09-28 9:45 ` Sebastian Moeller
2015-02-06 11:04 ` Sebastian Moeller [this message]
2014-09-28 11:48 ` Neil Shepperd
2014-09-28 12:22 ` Toke Høiland-Jørgensen
2014-10-01 5:20 ` Dave Taht
2014-10-01 7:57 ` Keith Duthie
2014-11-08 5:33 ` Aaron Wood
2014-11-09 18:27 ` Luke Hamburg
2014-10-01 12:37 ` Richard Weait
2014-11-06 15:45 ` leetminiwheat
2014-11-08 12:08 ` Sebastian Moeller
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=0556A811-405E-4FA2-B6F5-35DD1E108A87@gmx.de \
--to=moeller0@gmx.de \
--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