From: Dan Siemon <dan@coverfire.com>
To: Dave Taht <dave.taht@gmail.com>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] What is fairness, anyway? was: Re: finally... winning on wired!
Date: Fri, 13 Jan 2012 22:45:55 +0100 [thread overview]
Message-ID: <1326491155.8846.9.camel@neptune> (raw)
In-Reply-To: <CAA93jw7xKwdUeT7wFNoiM8RQp1--==Eazdo0ucc44vz+L1U06g@mail.gmail.com>
On Sun, 2012-01-08 at 01:40 +0100, Dave Taht wrote:
> On Thu, Jan 5, 2012 at 6:52 PM, Bob Briscoe <bob.briscoe@bt.com> wrote:
> >
> > In a nutshell, bit-rate equality, where each of N active users gets 1/N of
> > the bit-rate, was found to be extremely _unfair_ when the activity of
> > different users is widely different. For example:
> > * 5 light users all active 1% of the time get close to 100% of a shared link
> > whenever they need it.
> > * However, if instead 2 of these users are active 100% of the time, FQ gives
> > the other three light users only 33% of the link whenever they are active.
> > * That's pretty rubbish for a solution that claims to isolate each user from
> > the excesses of others.
>
> Without AQM or FQ, we have a situation where one stream from one user
> at a site, can eat more than 100% of the bandwidth.
>
> 1/u would be a substantial improvement!
Indeed I've found this to be the case. I've been using a Linux tc
configuration in both the upstream and downstream which is designed to
protect each host's bandwidth share and within that provide three
traffic classes with flow fairness (script link below). With this
configuration I no longer have to worry about other network traffic
interfering with a decent web experience or VoIP call.
http://git.coverfire.com/?p=linux-qos-scripts.git;a=blob;f=src-3tos.sh;hb=HEAD
--
Key ID: 133F6C3E
Key Fingerprint: 72B3 AF04 EFFE 65E4 46FF 7E5B 9297 18BA 133F 6C3E
next prev parent reply other threads:[~2012-01-13 21:46 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 0:40 [Bloat] " Dave Taht
2012-01-02 5:22 ` Eric Dumazet
2012-01-02 8:07 ` Dave Taht
2012-01-02 21:31 ` Dave Taht
2012-01-02 22:14 ` Albert Rafetseder
2012-01-02 22:33 ` Dave Taht
2012-01-04 15:25 ` [Bloat] What is fairness, anyway? was: " Jim Gettys
2012-01-04 16:16 ` Dave Taht
2012-01-04 17:23 ` Jim Gettys
2012-01-04 17:36 ` Justin McCann
2012-01-04 17:40 ` Eric Dumazet
[not found] ` <CAFkTFa89mOmbcOV1PWX3my04rK4NsEvyakcQV2j54qa0gzAViQ@mail.g mail.com>
2012-01-05 17:52 ` Bob Briscoe
2012-01-06 17:42 ` Jim Gettys
2012-01-06 18:09 ` Dave Taht
2012-01-06 19:57 ` Eric Dumazet
2012-01-06 20:34 ` Jonathan Morton
2012-01-07 19:42 ` Bob Briscoe
2012-01-07 22:16 ` Wesley Eddy
2012-01-08 0:40 ` Dave Taht
[not found] ` <CAA93jw7xKwdUeT7wFNoiM8RQp1--==Eazdo0ucc44vz+L1U06g@mail.g mail.com>
2012-01-09 5:38 ` Bob Briscoe
2012-01-11 7:26 ` Dave Taht
[not found] ` <CAA93jw4KJdYwrAuk7-yHDYCGBh1s6mE47eAYu2_LRfY45-qZ2g@mail.g mail.com>
2012-01-14 11:06 ` Bob Briscoe
2012-01-13 21:45 ` Dan Siemon [this message]
2012-01-14 15:55 ` Dave Taht
2012-01-04 16:22 ` Eric Dumazet
2012-02-05 0:24 ` George B.
2012-02-05 0:43 ` Jonathan Morton
2012-02-05 1:57 ` George B.
2012-02-05 2:05 ` john thompson
2012-02-05 7:39 ` Eric Dumazet
[not found] ` <CAA93jw68yntHkhETQ1a9-Azu7UXEuU9f5fgOsB25hvA240iApg@mail.gmail.com>
2012-02-05 14:24 ` Dave Taht
2012-02-05 17:53 ` Justin McCann
2012-02-05 18:21 ` Eric Dumazet
2012-01-14 16:35 Jesper Dangaard Brouer
2012-01-15 9:49 ` Dave Taht
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=1326491155.8846.9.camel@neptune \
--to=dan@coverfire.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.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