From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] happy 4th!
Date: Tue, 9 Jul 2013 08:04:39 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.00.1307090749480.8891@uplift.swm.pp.se> (raw)
In-Reply-To: <871u79x9kb.fsf@toke.dk>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1118 bytes --]
On Mon, 8 Jul 2013, Toke Høiland-Jørgensen wrote:
> Did a few test runs on my setup. Here are some figures (can't go higher
> than 100mbit with the hardware I have, sorry).
Thanks, much appreciated!
> Note that I haven't done tests at 100mbit on this setup before, so can't
> say whether something weird is going on there. I'm a little bit puzzled
> as to why the flows don't seem to get going at all in one direction for
> the rrul test. I'm guessing it has something to do with TSQ.
For me, it shows that FQ_CODEL indeed affects TCP performance negatively
for long links, however it looks like the impact is only about 20-30%.
What's stranger is that latency only goes up to around 230ms from its
200ms "floor" with FIFO, I had expected a bigger increase in buffering
with FIFO. Have you done any TCP tuning?
Would it be easy for you to do tests with the streams that "loads up the
link" being 200ms RTT, and the realtime flows only having 30-40ms RTT,
simulating downloads from a high RTT server and doing interactive things
to a more local web server.
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2013-07-09 6:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 19:33 Dave Taht
2013-07-04 5:57 ` Mikael Abrahamsson
2013-07-04 13:51 ` Michael Richardson
2013-07-04 15:48 ` Mikael Abrahamsson
2013-07-07 18:52 ` dpreed
2013-07-08 0:24 ` Mikael Abrahamsson
2013-07-08 17:03 ` Toke Høiland-Jørgensen
2013-07-09 3:24 ` Dave Taht
2013-07-09 6:04 ` Mikael Abrahamsson [this message]
2013-07-09 6:32 ` Dave Taht
2013-07-09 7:30 ` [Cerowrt-devel] [Codel] " Andrew McGregor
2013-07-09 13:09 ` Eric Dumazet
2013-07-09 7:57 ` [Cerowrt-devel] " Toke Høiland-Jørgensen
2013-07-09 12:56 ` [Cerowrt-devel] [Codel] " Eric Dumazet
2013-07-09 13:13 ` Toke Høiland-Jørgensen
2013-07-09 13:23 ` Eric Dumazet
2013-07-09 13:25 ` Toke Høiland-Jørgensen
2013-07-09 13:36 ` Eric Dumazet
2013-07-09 13:45 ` Toke Høiland-Jørgensen
2013-07-09 13:49 ` Eric Dumazet
2013-07-09 13:53 ` Toke Høiland-Jørgensen
2013-07-09 14:07 ` Eric Dumazet
2013-07-08 20:50 ` [Cerowrt-devel] " dpreed
2013-07-08 21:04 ` Jim Gettys
2013-07-09 5:48 ` Mikael Abrahamsson
2013-07-09 5:58 ` dpreed
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=alpine.DEB.2.00.1307090749480.8891@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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