From: Kathleen Nichols <nichols@pollere.com>
To: codel@bufferbloat.net
Subject: [Codel] question about "data center" models
Date: Thu, 03 May 2012 16:23:26 -0700 [thread overview]
Message-ID: <4FA3136E.3060502@pollere.com> (raw)
So, I thought I'd see what happens with a 1G bottleneck and a 5ms RTT.
I'm still checking
it out, but I thought I'd try to understand the concern. So, under a
constant heavy load,
codel will accept a 5ms standing queue. I got the impression this was a
concern. I'm
not exactly certain why. How much buffer is normally in the bottleneck?
If it's enough
for a "nominal" RTT of 100 ms, with drop tail it will just fill up and
stay there under
load. So, 100ms of delay. If it's at a RTT of 5ms, then the buffer will
fill up and give 5ms
of delay without any ability to absorb bursts. What is the normal
configuration?
Kathie
next reply other threads:[~2012-05-03 23:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 23:23 Kathleen Nichols [this message]
2012-05-03 23:36 ` Andrew McGregor
2012-05-04 2:00 ` Dave Taht
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/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FA3136E.3060502@pollere.com \
--to=nichols@pollere.com \
--cc=codel@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