From: Taraldsen Erik <erik.taraldsen@telenor.no>
To: Dave Taht <dave.taht@gmail.com>, Nils Andreas Svee <me@lochnair.net>
Cc: "Jonathan Morton" <chromatix99@gmail.com>,
"Toke Høiland-Jørgensen via Cake" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] STEAM tcp algo from CDN?
Date: Wed, 10 Mar 2021 07:04:02 +0000 [thread overview]
Message-ID: <194ad8c5177a4f06aca1c879097647c5@telenor.no> (raw)
In-Reply-To: <CAA93jw5vmqoRjD5OerJgWbD7FnZG4_PoSYffDRXCY6hdJU+o2A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1870 bytes --]
So to summarize, not quite certain which tcp algo they use. But everyone seems to agree that Steam does whatever they can to jam the pipe full
________________________________
Fra: Dave Taht <dave.taht@gmail.com>
Sendt: onsdag 10. mars 2021 01.57.09
Til: Nils Andreas Svee
Kopi: Jonathan Morton; Toke Høiland-Jørgensen via Cake; Taraldsen Erik
Emne: Re: [Cake] STEAM tcp algo from CDN?
I would really like them to use less flows - or BBR started up
separately with a 200+ms
interval between starts would be good....
On Tue, Mar 9, 2021 at 4:31 PM Nils Andreas Svee <me@lochnair.net> wrote:
>
> On Wed, 2021-03-10 at 01:14 +0200, Jonathan Morton wrote:
> > > On 9 Mar, 2021, at 10:20 pm, Dave Taht <dave.taht@gmail.com> wrote:
> > >
> > > 10-20 flows, cubic, last I looked. It's ugly.
> >
> > I can't confirm CUBIC from here, but it seems to be 4-8 flows in
> > parallel now. Latency to the national CDN is about 22ms over LTE, so
> > it's hard to distinguish CUBIC from anything else in particular; in
> > this range it would look a lot like NewReno. It seems to shut down
> > each flow and start a fresh one after about a minute.
> Seeing somewhere between 8-16 here I believe. IIRC I've seen you
> mention being located in Finland, if so we're probably on the same
> datacenter in Stockholm.
>
> The flows are probably not lasting long because the downloads are split
> into chunks, which according to my logs are at most 1 MB. Patches seem
> to work differently, those can be much larger (logs shows the largest
> one the past months was 137 MB, depends on the game I assume).
>
> --
> Best Regards,
> Nils
>
--
"For a successful technology, reality must take precedence over public
relations, for Mother Nature cannot be fooled" - Richard Feynman
dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729
[-- Attachment #2: Type: text/html, Size: 3121 bytes --]
prev parent reply other threads:[~2021-03-10 7:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 7:35 Taraldsen Erik
2021-03-09 20:20 ` Dave Taht
2021-03-09 23:14 ` Jonathan Morton
2021-03-10 0:31 ` Nils Andreas Svee
2021-03-10 0:57 ` Dave Taht
2021-03-10 7:04 ` Taraldsen Erik [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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=194ad8c5177a4f06aca1c879097647c5@telenor.no \
--to=erik.taraldsen@telenor.no \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=dave.taht@gmail.com \
--cc=me@lochnair.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