From: "Jerry Jongerius" <jerryj@duckware.com>
To: <bloat@lists.bufferbloat.net>
Subject: [Bloat] What is wrong with Microsoft's receive window auto-tuning?
Date: Mon, 1 Sep 2014 13:23:11 -0400 [thread overview]
Message-ID: <000001cfc609$697feb30$3c7fc190$@duckware.com> (raw)
I am noticing (via WireShark traces) at times that Microsoft's (Windows 7)
receive window auto-tuning goes horribly wrong, causing significant buffer
bloat. And at other times, the tuning appears to work just fine.
For example, BDP suggests a receive window of 750k, and most often Windows
tunes around 1MB -- but at other times, it will tune to 3.8MB (way more than
it should).
Is anyone aware of any research either pointing out how their tuning
algorithm works, or of known bugs/problems with the algorithm?
next reply other threads:[~2014-09-01 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 17:23 Jerry Jongerius [this message]
2014-09-11 17:05 ` Eric Dumazet
2014-09-11 17:40 ` Steinar H. Gunderson
2014-09-11 21:13 ` Eric Dumazet
2014-09-12 11:03 ` Jerry Jongerius
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='000001cfc609$697feb30$3c7fc190$@duckware.com' \
--to=jerryj@duckware.com \
--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