From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Steam's TCP analysis
Date: Fri, 27 Jan 2017 08:15:35 -0800 [thread overview]
Message-ID: <CAA93jw67=07cJXUS9kTqjvC=8i+saX_yB_QqwJQRHLHXrQ3EwQ@mail.gmail.com> (raw)
All over the net I hear of the bloated horrors steam and windows 10
updates are inflicting on people, and several saying that inbound
shaping isn't helping. I finally got two captures of a steam download
here:
https://github.com/tohojo/sqm-scripts/issues/43#issuecomment-275281826
And aside from some potential oddities (window, timestamp) didn't see
anything terribly odd in the first trace I got there. Could someone
take a look with smarter eyeballs than I have?
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
next reply other threads:[~2017-01-27 16:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 16:15 Dave Taht [this message]
2017-01-28 0:11 ` Benjamin Cronce
2017-01-28 0:26 ` Benjamin Cronce
2017-01-28 10:29 ` Yoshifumi Nishida
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='CAA93jw67=07cJXUS9kTqjvC=8i+saX_yB_QqwJQRHLHXrQ3EwQ@mail.gmail.com' \
--to=dave.taht@gmail.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