From: Georgios Amanakis <g_amanakis@yahoo.com>
To: cake@lists.bufferbloat.net
Subject: Re: [Cake] Per-host fairness
Date: Thu, 20 Oct 2016 23:08:36 -0400 [thread overview]
Message-ID: <1477019316.2635.1.camel@yahoo.com> (raw)
In-Reply-To: <mailman.3.1476806401.24997.cake@lists.bufferbloat.net>
Hi Sebastian,
> I probably would try to instantiate cake not on the wan but on
> a lan interface of the router and re-do the test without the “nat”
> option just to reduce the number of tested parts. If you should do
> this, please remember that ingress and egress are per interface, so
> downloads from the internet use the LAN-egress while internet-
uploads
> use LAN-ingress, so make sure to switch the bandwidth definitions for
> your two cake instances accordingly.
> Finally could you post the results of “tc -s qdisc” before,
> during and after your bit-torrent tests for the test you just
> reported and the LAN test in case you ago that route.
I tried what you suggested on the LAN interface (ingress: 900kbit/s,
egress: 3300kbit/s). Details follow.
> > and when doing simple
> > things (i.e. downloading from a couple of websites) the bandwidth
> > is
> > divided fair per-host, i.e 1:1 between A and B.
>
> Okay, does this stay fair if one of the hosts open a bunch of
> websites at the same time? Does the download test also give per-host
> fairness if the number of downloads is massively imbalanced between
> the hosts?
There seems to be a discrepancy here. If host A is downloading a file
(e.g. kernel.org) and host B opens a bunch of websites simultaneously
(e.g. "firefox arstechnica.com; firefox in.gr; firefox phoronix.com;
firefox cnn.com; firefox theguardian.co.uk") the following happens: for
the first 20 seconds host B gets 90% of the bandwidth and then it
slowly equilibrates to 50%-50%.
> > However, when one of
> > the hosts is using bittorrent, he also gets most of the bandwidth,
> > i.e.
> > if total ingress bandwidth is 3300kbit, A is using bittorrent and
> > gets
> > 2900kbit, B is downloading from a single website and gets 400kbit.
>
> Bit-torrent is a hard problem it seems, especially the cobalts
> branch that you test is supposed to better deal with it though so
> this is abit of a puzzle. How long are your tests? Are you looking
> only at a few seconds or something like >30 seconds (maybe the shaper
> needs time to reach equilibrium)? What happens in the upload during
> theses tests? I also wonder how many new torrent connections are
> established during the test or are the torrent flows long lived?
>
I am performing this test for 5 minutes, using the torrent for ubuntu-
16.10-desktop. Regarding new established torrent connections, these are
around 50 in this 5-minute interval. You *can* browse the web from host
B but there is notable latency. Pings to 8.8.8.8 are typically 300-
400msec.
Best regards,
George
next parent reply other threads:[~2016-10-21 3:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3.1476806401.24997.cake@lists.bufferbloat.net>
2016-10-21 3:08 ` Georgios Amanakis [this message]
2016-10-16 15:57 G. Amanakis
2016-10-16 17:30 ` G. Amanakis
2016-10-16 17:59 ` Sebastian Moeller
2016-10-18 1:33 ` Georgios Amanakis
2016-10-18 8:44 ` moeller0
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1477019316.2635.1.camel@yahoo.com \
--to=g_amanakis@yahoo.com \
--cc=cake@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