From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/deBloat] : Basic 4Mbit testing and partial log results
Date: Thu, 12 Jan 2012 22:10:57 -0800 [thread overview]
Message-ID: <4f0fcaf1d9243_21e53ffc46a292fc62020@sh1.rs.github.com.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/deBloat
Commit: d0c4d4f8b7f560962a3541760876cab48bbea0e4
https://github.com/dtaht/deBloat/commit/d0c4d4f8b7f560962a3541760876cab48bbea0e4
Author: Dave Taht <d@taht.net>
Date: 2012-01-12 (Thu, 12 Jan 2012)
Changed paths:
M src/debloat
A test/rtt/itest
A test/rtt/notes.org
Log Message:
-----------
Basic 4Mbit testing and partial log results
I put up some test results in the test/rtt directory. I
have more detailed logs too, but they point to SFQ working
really well to preserve interactive streams.
Trying to figure out to what extent red is working vs sfq
doing it's job is hard. I need to be monitoring end-to-end
stuff, and analyzing the packet captures on both sides.
My primary concern is with byte oriented red here and watching
iperf misbehave, taking 67 seconds to conclude a test that I
had specified 60 for on the 10 stream test. Did I end up with
~7 seconds of buffering in the high rate streams, delaying the
FIN/ACK process?
Or is it just iperf misbehaving? netperf seems not to...
reply other threads:[~2012-01-13 6:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4f0fcaf1d9243_21e53ffc46a292fc62020@sh1.rs.github.com.mail \
--to=noreply@github.com \
--cc=cerowrt-commits@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