General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Kenneth Porter <shiva@sewingwitch.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] DSLReports Speed Test doesn't like Remote Desktop
Date: Fri, 27 Aug 2021 08:36:59 -0700	[thread overview]
Message-ID: <A4127DA51130D688FE9B1092@[192.168.1.16]> (raw)
In-Reply-To: <133F6C06-4354-4E84-8D7A-AED43E00126D@gmail.com>

--On Friday, August 27, 2021 2:18 PM +0300 Jonathan Morton 
<chromatix99@gmail.com> wrote:

> A browser-based speed test like DSLreports depends heavily on the
> responsiveness of the browser itself.  It would appear that RDP
> interferes with that quite spectacularly, although I'm unsure exactly
> why.  The only advice I can give is "don't do that, then".

I've gotten good numbers from Xfinity's own speed test, and the Waveform 
test shows what I expect. I'm pretty sure I've gotten reasonable numbers 
from DSLReports in the past year, so this week's DSLReports test was quite 
surprising in sucking so badly. I did check the "low-fi" option to disable 
browser animations (and yet still got animations) so maybe DSLReports broke 
that and is trying to do browser animations in the same thread as the speed 
test.

I almost never have a problem with app responsiveness over the RDP 
connection, including Youtube on my 4k screen at 60 Hz. The one thing I 
don't virtualize is 3D stuff, notably gaming. It's actually impressive just 
how much stuff "just works" over RDP. (The two boxes ARE connected by only 
a 1 Gbit switch.)


  reply	other threads:[~2021-08-27 15:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26 23:25 Kenneth Porter
2021-08-27 10:18 ` Jonathan Morton
2021-08-27 15:36   ` Kenneth Porter [this message]
2021-08-27 21:56   ` Kenneth Porter
2021-08-28 19:36   ` Michael Richardson
2021-08-28 20:07     ` Jonathan Morton

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='A4127DA51130D688FE9B1092@[192.168.1.16]' \
    --to=shiva@sewingwitch.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