From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/deBloat] : An attempt to simulate voip a little bit.
Date: Sat, 07 Jan 2012 04:28:04 -0800 [thread overview]
Message-ID: <4f083a5464ae9_6a4f3f9b434572fc1149a0@sh1.rs.github.com.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 2699 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/deBloat
Commit: e656d9eb4256e89ab21eeec740ad79e840057eab
https://github.com/dtaht/deBloat/commit/e656d9eb4256e89ab21eeec740ad79e840057eab
Author: Dave Taht <d@taht.net>
Date: 2012-01-07 (Sat, 07 Jan 2012)
Changed paths:
A test/voip/25maerts.25stream.fping10.pfifo.txt
A test/voip/25maerts.25stream.fping10.qfq.txt
A test/voip/25maerts.25stream.fping10.sfq.gnu
A test/voip/25maerts.25stream.fping10.sfq.txt
A test/voip/pfifo_fast/t
A test/voip/pfifo_fast/t.10
A test/voip/pfifo_fast/t.50
A test/voip/pfifo_fast/t10.50
A test/voip/pfifofast2/fpingtest.voip
A test/voip/pfifofast2/parse
A test/voip/pfifofast2/vsnetperf50_maerts_stream.data
A test/voip/pfifofast2/vsnetperf50_maerts_stream.summary
A test/voip/qfq/fpingtest.voip
A test/voip/qfq/parse
A test/voip/qfq/vsnetperf50_maerts_stream.data
A test/voip/qfq/vsnetperf50_maerts_stream.summary
A test/voip/sfq/fpingtest.voip
A test/voip/sfq/parse
A test/voip/sfq/t10.50.2.txt
A test/voip/sfq/t10.50.3.txt
A test/voip/sfq/t10.50.txt
A test/voip/sfq/unloaded.summary
A test/voip/sfq/vsiperf1.2.data
A test/voip/sfq/vsiperf1.2.summary
A test/voip/sfq/vsiperf1.3.data
A test/voip/sfq/vsiperf1.3.summary
A test/voip/sfq/vsiperf10.data
A test/voip/sfq/vsiperf10.summary
A test/voip/sfq/vsiperf50.2.data
A test/voip/sfq/vsiperf50.2.summary
A test/voip/sfq/vsiperf50.data
A test/voip/sfq/vsiperf50.summary
A test/voip/sfq/vsnetperf20.data
A test/voip/sfq/vsnetperf20.summary
A test/voip/sfq/vsnetperf50_maerts_stream.data
A test/voip/sfq/vsnetperf50_maerts_stream.summary
A test/voip/sfq/wtf2
A test/voip/summary.org
Log Message:
-----------
An attempt to simulate voip a little bit.
I sat down and wondered what would happen with a 10ms stream
beating against a network with sfq and qfq and pfifo_fast on it.
Everything downstream (3 hops) is running old sfq, and I'm
running 'new' sfq with the head of line fix in it against
all that. The results are basically that the downstream
boxes do a pretty good job on streams regardless of the
fact they were running old sfq, but I still need to
check a few things and collect all the related data.
I just consider this a start towards coming up with
automated tests that can use cdf in order to show valid
results. The data is too noisy to look at otherwise,
and that also means that all parameters and results
need to be looked at...
I do not in any way draw any conclusions from these
plots.
For example, along the way, iperf started acting up for some
reason - it would terminate early... and I switched to
netperf because of that...
reply other threads:[~2012-01-07 12:28 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=4f083a5464ae9_6a4f3f9b434572fc1149a0@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