General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Mario Hock <mario.hock@kit.edu>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Win10 Updates vs cake
Date: Fri, 22 Dec 2017 10:12:45 +0100	[thread overview]
Message-ID: <d6d61a2b-e426-df52-938f-c2161ea5107e@kit.edu> (raw)
In-Reply-To: <3657B600-407D-46A5-BE00-BE0088096FA7@gmail.com>

Hi,

except from buffer bloat performance can also be degraded by an 
increased packet loss probability.

Can you also track packet loss rates / packet loss probability? And also 
throughput/progress of the Windows update connections?

If the reason actually is that FastTCP does not respond to congestion in 
a fair manner (as Ryan Mounce suggested) than you should see high packet 
loss (for all connections), high throughput for the Windows update 
connections and very low throughput for regular TCP connections.

Also, it would be interesting to see what happens to fixed bit rate UDP 
streams.

Best, Mario


Am 22.12.2017 um 03:01 schrieb Rich Brown:
> I'm using LEDE 17.01.4 on my Archer C7v2. I have a 7mbps/768kbps ADSL2+ connection through Fairpoint. The modem stats page shows its "attainable rates" (kbps): 13330/1272 and Rates: 8271/1181. My SQM settings are:
> 
> Download: 7000 (kbps)
> Upload: 925
> Queue Disc: Cake/piece_of_cake.qos
> Link Layer: ATM/44 bytes overhead
> Advanced Options: default
> 
> I have noticed that Win10 updates cause the network connection to become unusable for other services/people, as if I had bufferbloat. But ping times remain stable - they jump from ~20-22 msec unloaded to 40-50 msec.
> 
> Experiments I have tried:
> 
> - Setting download speed to 5000 makes the connection usable for other people, although the ping times remain about the same (40-50 msec)
> 
> - Setting the download speed to 8600 still keeps ping times down, but that really harms other people's performance.
> 
> - The link rates (download and upload) seem to track the SQM setting, measured with both YAMon and the built-in real-time graphs.  I get ~6,000 kbps with a 7000 download setting, I got ~3,000kbps at the 5000 setting. I get ~8500 kbps after setting download to 8600.
> 
> - This doesn't seem to happen when I'm downloading other kinds of files (I haven't tried torrenting files...) Downloading non-Win10 update files seems to leave the connection in a fairly responsive state.
> 
> Any thoughts? What other experiments should I make? Thanks!
> 
> Rich
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
> 

  parent reply	other threads:[~2017-12-22  9:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-22  2:01 Rich Brown
2017-12-22  2:55 ` Ryan Mounce
2017-12-22  3:57   ` Ryan Mounce
2017-12-22  4:03     ` Jonathan Morton
2017-12-22  5:26     ` Jonathan Morton
2017-12-29  4:49       ` Ryan Mounce
2017-12-22  9:17     ` Kevin Darbyshire-Bryant
2017-12-22 13:07       ` Rich Brown
2017-12-28 17:48   ` Benjamin Cronce
2017-12-29  4:44     ` Ryan Mounce
2017-12-22  9:12 ` Mario Hock [this message]
     [not found] <mailman.56.1513933967.3659.bloat@lists.bufferbloat.net>
2017-12-22 13:13 ` Rich Brown

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=d6d61a2b-e426-df52-938f-c2161ea5107e@kit.edu \
    --to=mario.hock@kit.edu \
    --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