From: Kathleen Nichols <nichols@pollere.com>
To: codel@lists.bufferbloat.net
Subject: Re: [Codel] Worst case conditions - large RTT
Date: Wed, 09 May 2012 13:42:42 -0700 [thread overview]
Message-ID: <4FAAD6C2.5070304@pollere.com> (raw)
In-Reply-To: <4FAAD534.2030100@superduper.net>
In the paper, I show the 500 RTT case. I also ran some at 750ms and 1 sec.
The utilization is not as good as the smaller RTTs but it was still good.
Maybe you can try to create the situation you are thinking of?
On 5/9/12 1:36 PM, Simon Barber wrote:
> Codel assesses the minimum delay over a fixed time period (the interval)
> - what happens when the interval is much smaller that the RTT. For
> example a tcp stream is experiencing a 2 second RTT (perhaps due to
> bufferbloat at some point), yet the interval is 100ms. The TCP
> implementation is a poor one that will ACK a window at a time. Here
> codel will drop excessively, and cause low throughput?
>
> Simon
> _______________________________________________
> Codel mailing list
> Codel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/codel
prev parent reply other threads:[~2012-05-09 20:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 20:36 Simon Barber
2012-05-09 20:41 ` Dave Taht
2012-05-09 21:08 ` Jim Gettys
2012-05-09 20:42 ` Kathleen Nichols [this message]
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=4FAAD6C2.5070304@pollere.com \
--to=nichols@pollere.com \
--cc=codel@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