From: "David Täht" <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
mark@santcroos.net, sytsevg@gmail.com
Subject: [Bloat] Performance simulation of buffer bloat in routers
Date: Tue, 11 Oct 2011 13:46:04 +0200 [thread overview]
Message-ID: <4E942C7C.6020506@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1393 bytes --]
while catching up on the literature and reading the following:
http://staff.science.uva.nl/~delaat/netbuf/bufferbloat_MS-SG.pdf
And "Performance simulation of buffer bloat in routers"
http://staff.science.uva.nl/~delaat/netbuf/bufferbloat_BG-DD.pdf
I note that while otherwise looking very good at first scan, it would be
nice to have several additions to the second paper. I was unable to find
the email addresses of the authors of the second paper, so I'm cc'ing
the first in the hope that they can be contacted.
A) Having a copy of the model's code used would be VERY useful to us...
B) The paper stops the experiments at 500 buffers.
1) the range 1064-1256 is the effective real-world default for ethernet
on most versions of Linux. It would be useful to have a model and
analysis for what happens in the real world (although I suspect they
would have to increase the test duration). I'd like to see theory and
reality line up a little better than they have to date.
2) Effective buffering, with retries, in wireless devices is far, far,
far, in excess of that, at least at present, for many devices. For
reference, going to say, 10,000 buffers, would be good. I look forward
to seeing chaotic effects.
C) The TCP algorithm in use is not documented
D) The distance of the paths is short. Simulating a longer distance path
(say, 100ms) would be interesting.
--
Dave Täht
[-- Attachment #2: dave_taht.vcf --]
[-- Type: text/x-vcard, Size: 204 bytes --]
begin:vcard
fn;quoted-printable:Dave T=C3=A4ht
n;quoted-printable:T=C3=A4ht;Dave
email;internet:dave.taht@gmail.com
tel;home:1-239-829-5608
tel;cell:0638645374
x-mozilla-html:FALSE
version:2.1
end:vcard
reply other threads:[~2011-10-11 11:46 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=4E942C7C.6020506@gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=mark@santcroos.net \
--cc=sytsevg@gmail.com \
/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