From: Sebastian Moeller <moeller0@gmx.de>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: "bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] RED against bufferbloat
Date: Wed, 25 Feb 2015 17:54:49 +0100 [thread overview]
Message-ID: <012AA248-69C5-4805-8CA7-1961AE04D7AE@gmx.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1502251433230.4007@uplift.swm.pp.se>
Hi Mikael,
On Feb 25, 2015, at 14:36 , Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> On Wed, 25 Feb 2015, Sebastian Moeller wrote:
>
>> The only argument for ingress shaping on the CPE is that this allows the end user to define her own QOS criteria independent of the ISPs wishes. Best of both worlds would be user configurable QOS-shaping on the slam/bras/whatever…
>
> As I said before, doing FQ_CODEL in the AR is an expensive proposition for medium and high speed access.
Well a vectoring DSLAM is not too wimpy and needs to do plenty of processing per line, so fq_codel on there should be more finically sane than on a device with more concurrent users, I would guess...
> So if this could successfully be pushed to the CPE it would mean it would be more widely deployed.
But there we face the same problem, the wimpy CPEs that ISPs like to distribute do not have enough pomp for shaping a reasonably fast lane, the saving grace might be that end customers can upgrade on their own cost. And I notice a number of specialized home routers appearing on the market targeting people wiling to spend $$ for better behavior under load.
>
> I am very much aware that this is being done (I have done it myself), but my question was if someone had actually done this in a lab and found out how well it works in RRUL tests etc.
Not in the lab, no; I have no lab, but I used RRUL iteratively to figure out empirically what shaping percentage I need on my line to keep latency under load in bounds I consider reasonable. In my case DTAG vdsl50 this turned out to be 90% of downlink sync and 95% of uplink sync (but I since learned that DTAG has a BRAS policer that has a lower rate than the VDSL-line, so I guess I was closer to 95% and 99% percent of the BRAS policer, but heaven knows which encapsulation the BRAS accounts for…)
So I would guess the collection of cerowrt users should be able to cough up a number of empirical shaping percentages for different link speeds and technologies.
Here is my data, the empirically derived shaping values puzzled me until I learned about the BRAS policer. I had expected that the uplink shaper could run almost at 100%, which turned out to be correct if referenced to the BRAS policer and not the vdlx sync. Anyway here is my data, maybe others want to add their’s:
Tech downlink_kbps uplink_kbps CPE_shaper
sync ISP_policed CPE_shaped sync ISP_policed CPE_shaped overhead_B linklayer
VDSL2.vectoring 51390 45559 46178 10047 9460 9500 16 ethernet
Best Regards
Sebastian
>
> --
> Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2015-02-25 16:55 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 15:43 sahil grover
2015-02-24 16:13 ` Matt Mathis
2015-02-24 22:39 ` Kathleen Nichols
2015-02-25 6:46 ` Mikael Abrahamsson
2015-02-25 6:54 ` David Lang
2015-02-25 6:59 ` Mikael Abrahamsson
2015-02-25 8:29 ` Alex Elsayed
2015-02-25 8:06 ` Bob Briscoe
2015-02-25 8:42 ` Alex Elsayed
2015-02-25 9:18 ` Michael Welzl
2015-02-25 9:29 ` Sebastian Moeller
2015-02-25 10:10 ` Michael Welzl
2015-02-25 10:24 ` Toke Høiland-Jørgensen
2015-02-25 10:47 ` Mikael Abrahamsson
2015-02-25 11:04 ` Toke Høiland-Jørgensen
2015-02-25 18:39 ` Bill Ver Steeg (versteb)
2015-02-26 9:01 ` MUSCARIELLO Luca IMT/OLN
2015-02-26 10:39 ` Mikael Abrahamsson
2015-02-26 10:41 ` Toke Høiland-Jørgensen
2015-02-26 10:44 ` Mikael Abrahamsson
2015-02-26 10:51 ` Toke Høiland-Jørgensen
2015-02-26 10:59 ` Sebastian Moeller
2015-02-26 11:12 ` Jonathan Morton
2015-02-27 0:26 ` Dave Taht
2015-02-26 10:45 ` Sebastian Moeller
2015-02-26 11:34 ` Jonathan Morton
2015-02-26 12:59 ` Mikael Abrahamsson
2015-02-26 11:26 ` MUSCARIELLO Luca IMT/OLN
2015-02-26 12:57 ` Mikael Abrahamsson
2015-02-25 13:25 ` Sebastian Moeller
2015-02-25 13:36 ` Mikael Abrahamsson
2015-02-25 13:38 ` Toke Høiland-Jørgensen
2015-02-25 14:05 ` Mikael Abrahamsson
2015-02-25 18:51 ` Bill Ver Steeg (versteb)
2015-02-25 14:16 ` MUSCARIELLO Luca IMT/OLN
2015-02-25 16:09 ` Mikael Abrahamsson
2015-02-25 17:34 ` MUSCARIELLO Luca IMT/OLN
2015-02-25 17:56 ` Jonathan Morton
2015-02-26 12:54 ` Mikael Abrahamsson
2015-02-26 14:06 ` MUSCARIELLO Luca IMT/OLN
2015-02-26 14:18 ` Mikael Abrahamsson
2015-02-26 15:18 ` MUSCARIELLO Luca IMT/OLN
2015-02-26 17:04 ` Dave Taht
2015-02-26 18:07 ` Dave Taht
2015-02-26 18:33 ` [Bloat] RE : " luca.muscariello
2015-02-26 18:59 ` [Bloat] " Mikael Abrahamsson
2015-02-26 19:44 ` Bill Ver Steeg (versteb)
2015-02-26 20:42 ` Jonathan Morton
2015-02-26 21:50 ` Dave Taht
2015-02-25 16:54 ` Sebastian Moeller [this message]
2015-02-25 10:54 ` Michael Welzl
2015-02-25 11:24 ` Toke Høiland-Jørgensen
2015-02-25 12:08 ` Jonathan Morton
2015-02-25 19:04 ` David Lang
2015-02-25 19:30 ` Michael Welzl
2015-02-25 9:31 ` Alex Elsayed
2015-02-25 10:37 ` Michael Welzl
2015-02-25 10:54 ` Alex Elsayed
2015-02-25 17:28 ` Bob Briscoe
2015-02-25 18:03 ` Dave Taht
2015-02-26 9:36 ` Sebastian Moeller
2015-02-25 17:57 ` Dave Taht
2015-02-25 19:25 Hal Murray
2015-02-25 20:00 ` 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=012AA248-69C5-4805-8CA7-1961AE04D7AE@gmx.de \
--to=moeller0@gmx.de \
--cc=bloat@lists.bufferbloat.net \
--cc=swmike@swm.pp.se \
/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