From: noreply@github.com
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/deBloat] d96e6a: Basic Latency under load results - 100Mbit, pfifo_...
Date: Sun, 1 Jan 2012 09:33:58 -0800 [thread overview]
Message-ID: <20120101173358.4EEC442651@smtp1.rs.github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/dtaht/deBloat
Commit: d96e6a6616e4ec8830af71a32fb22fc3d2616608
https://github.com/dtaht/deBloat/commit/d96e6a6616e4ec8830af71a32fb22fc3d2616608
Author: Dave Taht <d@taht.net>
Date: 2012-01-01 (Sun, 01 Jan 2012)
Changed paths:
M test/ftest.lua
M test/ftest.org
A test/results/basic_latency_under_load.org
Log Message:
-----------
Basic Latency under load results - 100Mbit, pfifo_fast, sfq, qfq
I finally assembled enough infrastructure to do a test, collect
the data, and plot the results in a form that is easily understood.
Driven by org-mode. I still would like to generate the plots
statically and link them into the text and do html...
and there are zillion other tests to run, but the highlights
are:
WIRED
TXQUEUELEN=1000
BANDWIDTH=100Mbit
BQL=4500 (byte queue limits)
1 iPerf induces 10-12ms latency w/pfifo_fast
10 iPerfs induces ~107 ms latency w/pfifo fast
10 IPerfs induces ~2.8 ms latency w/sfq
10 iPerfs induces ~1.7 ms latency with staqfq
reply other threads:[~2012-01-01 17:33 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=20120101173358.4EEC442651@smtp1.rs.github.com \
--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