From: Rich Brown <richb.hanover@gmail.com>
To: Hector Ordorica <hechacker1@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Proper AQM settings for my connection?
Date: Sat, 21 Dec 2013 00:01:27 -0500 [thread overview]
Message-ID: <690EEC3B-8E4D-439E-84ED-375104FF2C43@gmail.com> (raw)
In-Reply-To: <CAMNY_1UqXuN31WjpmOH849iaQh1UizpbsFrWxX7EBFgN8AM0hg@mail.gmail.com>
On Dec 20, 2013, at 11:32 PM, Hector Ordorica <hechacker1@gmail.com> wrote:
> I'm running 3.10.13-2 on a WNDR3800, and have used the suggested
> settings from the latest draft:
>
> http://www.bufferbloat.net/projects/cerowrt/wiki/Setting_up_AQM_for_CeroWrt_310
>
> I have a 30Mb down / 5Mb upload cable connection.
>
> With fq_codel, even undershooting network upload bandwidth by more
> than 95%, I'm seeing 500ms excessive upload buffering warnings from
> netalyzr. Download is ok at 130ms. I was previously on a 3.8 release
> and the same was true.
I have seen the same thing, although with different CeroWrt firmware. Netalyzr was reporting
> 500 msec buffering in both directions.
However, I was simultaneously running a ping to Google during that Netalyzr run, and the
ping times started at ~55 msec before I started Netalyzr, and occasionally they would bump
up to 70 or 80 msec, but never the long times that Netzlyzr reported...
I also reported this to the Netalyzr mailing list and they didn’t seem surprised. I’m not sure how to interpret this.
> With pie (and default settings), the buffer warnings go away:
>
> http://n2.netalyzr.icsi.berkeley.edu/summary/id=43ca208a-32182-9424fd6e-5c5f-42d7-a9ea
>
> And the connection performs very well while torrenting and gaming.
>
> Should I try new code? Or can I tweak some variables and/or delay
> options in scripts for codel?
A couple thoughts:
- There have been a bunch of changes between 3.10.13-2 and the current version (3.10.24-5, which seems pretty stable). You might try upgrading. (See the “Rough Notes” at the bottom of http://www.bufferbloat.net/projects/cerowrt/wiki/CeroWrt_310_Release_Notes for the progression of changes).
- Have you tried a more aggressive decrease to the link speeds on the AQM page (say, 85% instead of 95%)?
- Can we get more corroboration from the list about the behavior of Netalyzer?
Rich
next prev parent reply other threads:[~2013-12-21 5:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-21 4:32 Hector Ordorica
2013-12-21 5:01 ` Rich Brown [this message]
2013-12-21 5:16 ` Dave Taht
2013-12-21 5:38 ` Hector Ordorica
2013-12-21 5:47 ` Hector Ordorica
2013-12-21 10:40 ` Sebastian Moeller
2013-12-21 10:32 ` 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=690EEC3B-8E4D-439E-84ED-375104FF2C43@gmail.com \
--to=richb.hanover@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=hechacker1@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