From: Dave Taht <dave.taht@gmail.com>
To: Rich Brown <richb.hanover@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Better results from CeroWrt 3.10.28-16
Date: Sun, 2 Mar 2014 18:00:10 -0800 [thread overview]
Message-ID: <CAA93jw6iuPtmw7TqqAdmFqwqUjYVHySymB1d4TNncdRBDE0DJg@mail.gmail.com> (raw)
In-Reply-To: <3C58F2F0-60C0-4EC3-A45F-6895227DC889@gmail.com>
it's in tc's output
qdisc nfq_codel 120: parent 1:12 limit 1001p flows 1024 quantum 300
target 14.8ms interval 109.8ms
Sent 122649261 bytes 332175 pkt (dropped 129389, overlimits 0 requeues 0)
^^^^^^
backlog 0b 0p requeues 0.
maxpacket 0 drop_overlimit 0 new_flow_count 37646 ecn_mark 0
new_flows_len 1 old_flows_len 2
It's late in england. going to bed before ietf tomorrow/
(I don't have a mac anymore and never thought to do a caipture at this rate.
I think the mac is iw4, but as we have 4 uploads going we are
effectively iw16 at
rrul startup, and yet, here we are trying to cut latencies to 15ms.
what I'm interested in determining is if the mac flows are experiencing RTOs,
and/or falling back to iw2...
For way more detail on the joys of iwX at high and low bandwidths:
https://datatracker.ietf.org/doc/rfc6928/?include_text=1
JG also has a rant on iw10 considered harmful. This is iw4 considered harmful
at speeds below 2mbit....
I have been trying to come up with a way to for default gws to communicate
a good iw size for a while and/or have a plot of behaviors at this speed.
On Sun, Mar 2, 2014 at 5:49 PM, Rich Brown <richb.hanover@gmail.com> wrote:
> Dave,
>
>> Target 30ms would be interesting. 30+ % packet loss on this test (and
>> your link is still operable!)
>
> Wait. How can you detect the packet loss from the data I sent along?
>
>> At your speed range the behavior of the tcp upload is governed by the
>> initial window size more than anything else. I doubt the
>> mac adjusts that properly so it keeps hammering away at it... my
>> concern from looking at your upload graphs was that you were
>> actually getting hammered so hard you were actually going through RTO
>> (receive timeout) on the uploads.
>
> Yuck. That would be bad.
>
> re: Wireshark. I'll try to get it soon.
>
> Thanks.
>
> Rich
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next prev parent reply other threads:[~2014-03-03 2:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-02 21:18 Rich Brown
2014-03-02 21:41 ` Dave Taht
2014-03-02 21:48 ` Sebastian Moeller
2014-03-03 1:38 ` Rich Brown
2014-03-05 18:52 ` Sebastian Moeller
2014-03-02 21:51 ` Aaron Wood
2014-03-02 22:19 ` Dave Taht
2014-03-03 1:27 ` Rich Brown
2014-03-03 1:41 ` Dave Taht
2014-03-03 1:43 ` Dave Taht
2014-03-03 1:49 ` Rich Brown
2014-03-03 2:00 ` Dave Taht [this message]
2014-03-03 2:28 ` Rich Brown
2014-03-03 8:51 ` Dave Taht
2014-03-03 8:53 ` Dave Taht
2014-03-03 13:35 ` Rich Brown
2014-03-03 13:43 ` Toke Høiland-Jørgensen
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=CAA93jw6iuPtmw7TqqAdmFqwqUjYVHySymB1d4TNncdRBDE0DJg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=richb.hanover@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