From: Juliusz Chroboczek <jch@pps.jussieu.fr>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] SFB and Dan Siemon's tests
Date: Sun, 03 Apr 2011 20:19:22 +0200 [thread overview]
Message-ID: <87vcyv19lh.fsf@trurl.pps.jussieu.fr> (raw)
Hi,
I've finally found some time to try to understand Dan Siemon's results
on
http://www.coverfire.com/archives/2011/02/21/network-latency-experiments/
That's some excellent work, Dan, a lot of thanks for it.
If I read it right, the BDP is 5 packets (4Mbit/s times 15ms), and SFB
is being run with a per-flow queue length of 20 packets (the default);
hence, it should be able to swallow the bursts necessary in order to
fill the link. The chaotic variations in latency, as well as the high
packet loss, indicate that either there's something wrong with the
implementation, or that somebody somewhere is sending massive bursts of
packets that sfb is discarding, as it is designed to do.
It would be good to have a graph of packet loss as a function of time,
in order to check if SFB is converging too slowly in this case.
-- Juliusz
reply other threads:[~2011-04-03 18:19 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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vcyv19lh.fsf@trurl.pps.jussieu.fr \
--to=jch@pps.jussieu.fr \
--cc=bloat@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