General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: David Lang <david@lang.hm>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] I feel an urge to update this
Date: Thu, 25 Sep 2014 10:08:32 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1409251002540.14735@uplift.swm.pp.se> (raw)
In-Reply-To: <alpine.DEB.2.02.1409250026180.13899@nftneq.ynat.uz>

On Thu, 25 Sep 2014, David Lang wrote:

> well, even if you have a 10GE connection, you don't know how heavily 
> it's going to be used.

No, but I will have a hunch. I don't need to *know*, I need to have a 
decent probability of being right.

> what happens if the wrong hint is given? (either accidently or maliciously)

Then you get IW10 instead of IW4. Right now if I am correct, Google does 
IW10 all across the board.

> The approach of starting slow and ramping up works well, except in the 
> case where you have lots of very short connections. So I don't see a 
> benefit of trying to hint slowness. There may be some value in hinting 
> for faster ramp-ups, but what will that do to fairness with existing 
> systems?

In my world, core network congestion isn't something that is permanent and 
continous, but an anomaly. So since the only port that should be 
congesting is my access port, I don't care about fairness. Also, we're not 
talking about starting off with a 1M TCP window to blast a huge chunk of 
data down the wire, we're talking about perhaps being a bit more agressive 
in increasing the window from a slightly higher initial level, let's say 
IW10 and instead of doubling, tripling window size, if the client hints 
they have a fast connection, and if the client says they have a slow 
connection, IW4 and increase 1.5x instead?

Use same mechanisms as today, but tweak them to be a bit more or less 
agressive depending on what the client has hinted.

I mean, why do we send MSS in TCP? Couldn't we just have a generic probing 
mechanism to test what MTU works? Well, that would be inefficient, so MSS 
helps. Same here.

> But we have a number of companies who want to have things downloaded and 
> used as quickly as possible, so if this sort of thing really does help, 
> then I would expect that they would be experimenting with tweaking the 
> TCP stack to ramp up faster (although, you would also be expecting 
> outcrys about "how dare $bigcompany ignore the TCP defaults and be more 
> agressive, that doesn't compete fairly with $normaltraffic)

Errr, google and IW10? So, already done!?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

  reply	other threads:[~2014-09-25  8:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-19 23:33 Dave Taht
2014-09-20  9:03 ` Steinar H. Gunderson
2014-09-20 15:55   ` Jonathan Morton
2014-09-20 16:47     ` Michael Welzl
2014-09-23  5:48 ` Mikael Abrahamsson
2014-09-23  8:31   ` Jonathan Morton
2014-09-25  4:16   ` David Lang
2014-09-25  5:32     ` Mikael Abrahamsson
2014-09-25  7:35       ` David Lang
2014-09-25  8:08         ` Mikael Abrahamsson [this message]
2014-09-25 11:00           ` David Lang
2014-09-25 13:00             ` Mikael Abrahamsson
2014-09-25 13:25               ` Dave Taht
2014-09-25 14:35                 ` Mikael Abrahamsson
2014-09-25 16:09       ` Rick Jones
2014-09-25 17:26         ` Mikael Abrahamsson
2014-09-25 17:49           ` Rick Jones
2014-09-27  8:59             ` Manolis Sifalakis
2014-09-29 17:28               ` Rick Jones
2014-10-04 19:56                 ` Manolis Sifalakis

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=alpine.DEB.2.02.1409251002540.14735@uplift.swm.pp.se \
    --to=swmike@swm.pp.se \
    --cc=bloat@lists.bufferbloat.net \
    --cc=david@lang.hm \
    /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