From: Michael Richardson <mcr+ietf@sandelman.ca>
To: cloneman <bufferbloat@flamingpc.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Windows 10 updates multhread limit Feature request to Microsoft
Date: Sun, 29 Mar 2020 12:51:12 -0400 [thread overview]
Message-ID: <14920.1585500672@localhost> (raw)
In-Reply-To: <CABQZMoLEz_EB6PY2Z7cDdOF+eWh=J5i6Pj_ZqP4i3WXtBgnkvw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1545 bytes --]
cloneman <bufferbloat@flamingpc.com> wrote:
> I don't know if the Windows 10 updates multithreading problem is still
> relevant for many users, but it certainly still affects me as user with
> low bufferbloat, low latency, and only moderate bandwidth (50mbit , 4ms
> idle, ~9ms loaded)
> In any case, I have submitted official feedback to microsoft, as I've
> exhausted any possible workarounds on my end short of implementing a
> Windows update cache server on my LAN (go figure, apparently the cache
> servers download with a small number of threads).
I guess either because the person implementing the cache system didn't work
as hard, or because they recognized they needed to do this in the "background"
> After posting this link -- I'm done advocating for this issue. I think
> valve steam has made some improvements, they still use many threads, but
> somehow, it doesn't create as many issues.There seems to be no interest in
> most discussion forums to explore this with any depth -- or even admit that
> 20 connections to 1-2 servers is problematic.
This is where some of the desire to have a "worse than best effort" queue
came from :-)
> Feedback hub link
> https://aka.ms/AA7zg1r
Not a public link, I think.
What's sad is that Windows 2000 was the only implementation of the diffedge
that we needed to make end-system driven QoS work, and then they abandonned
it.
--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
-= IPv6 IoT consulting =-
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2020-03-29 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 6:25 cloneman
2020-03-29 16:51 ` Michael Richardson [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/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=14920.1585500672@localhost \
--to=mcr+ietf@sandelman.ca \
--cc=bloat@lists.bufferbloat.net \
--cc=bufferbloat@flamingpc.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