From: Jonathan Morton <chromatix99@gmail.com>
To: mandy ahuja <mandyahuja013@gmail.com>
Cc: codel@lists.bufferbloat.net
Subject: Re: [Codel] Regarding BDP, window size and queue-size for codel in ns2
Date: Tue, 3 Mar 2015 21:34:01 +0200 [thread overview]
Message-ID: <CAJq5cE3jFsVBN=bzP105FcohK88HBm7Zbhn5cat3CTCNOwoNMA@mail.gmail.com> (raw)
In-Reply-To: <CALbqCD4RcDewKadAZccm5rsaTV9FeaVO7dCKk3mT52dpjPA28g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]
I recommended earlier to run Codel experiments with a very large buffer,
since Codel will keep it under control. For experimental rigour, you should
also run experiments involving other queue modes with the same buffer size,
and observe how well or badly each mode controls it.
As for receive window size, you should make that large enough that you will
notice the resulting delay easily. Modern operating systems will happily
use receive windows of several megabytes in default configurations; this
results in impressive delays at relatively low bandwidths. I've seen 45
seconds at 512Kbps.
You might also try setting up multiple simulated hosts with different
receive window sizes - including some sensibly small ones, such as the
65535 bytes which is the limit for TCP stacks without window scaling - and
see how they compete on the same congested link. This might give you some
insight into why such large windows seem desirable to those unaware of AQM,
and why they become mostly irrelevant when good AQM is introduced.
- Jonathan Morton
[-- Attachment #2: Type: text/html, Size: 1126 bytes --]
prev parent reply other threads:[~2015-03-03 19:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 17:27 [Codel] Regarding BDP,window " mandy ahuja
2015-03-03 19:34 ` Jonathan Morton [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='CAJq5cE3jFsVBN=bzP105FcohK88HBm7Zbhn5cat3CTCNOwoNMA@mail.gmail.com' \
--to=chromatix99@gmail.com \
--cc=codel@lists.bufferbloat.net \
--cc=mandyahuja013@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