From: <erik.taraldsen@telenor.com>
To: <me@lochnair.net>
Cc: <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Recomended HW to run cake and fq_codel?
Date: Wed, 3 May 2017 05:36:45 +0000 [thread overview]
Message-ID: <1493789805885.56806@telenor.com> (raw)
In-Reply-To: <1493727080.1510042.962956680.40220FCB@webmail.messagingengine.com>
> Fra: Nils Andreas Svee <me@lochnair.net>
>
> just fine, but I'd probably pick the ER-X-SFP for the beefier CPU, if
> only to get some extra headroom.
Then ER-X-SFP it is.
>DSL tends to suck pretty (read: very) bad without proper shaping, I
> know. On that note, are you planning to run an AQM on both ends of the
> bottleneck, or shape ingress traffic via a IFB device? CAKE helps a lot
> when running on ingress, but it can't come close to running on both
> ends.
I intended to only shape on egress for this experiement. Let downstream be handled by the BRAS's policies (Juniper ERX in our case). Most of the customer "speed" complaints come from not throughput but latency. And that latency is mostly ADSL/VDSL customers with large uploads to cloud services. So I think that we will by handling the upstream better make a large improvement. But, hey, I call it an experiemnt because it is an experiemnt. If we see significant improvements by using IFB for downstream as well. Then we will try to see what we can do to implement this.
-Erik
next prev parent reply other threads:[~2017-05-03 5:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.430.1493386395.3609.cake@lists.bufferbloat.net>
2017-04-28 16:39 ` Lochnair
2017-05-02 10:34 ` erik.taraldsen
2017-05-02 12:11 ` Nils Andreas Svee
2017-05-02 17:36 ` David Lang
2017-05-03 5:36 ` erik.taraldsen [this message]
2017-05-03 6:51 ` Sebastian Moeller
2017-05-03 7:27 ` erik.taraldsen
2017-05-03 8:24 ` Sebastian Moeller
2017-05-03 11:14 ` erik.taraldsen
[not found] ` <mailman.433.1493397541.3609.cake@lists.bufferbloat.net>
2017-04-28 18:07 ` Tristan Seligmann
[not found] <mailman.1.1493740801.18318.cake@lists.bufferbloat.net>
2017-05-02 18:44 ` Pete Heist
2017-05-03 5:59 ` erik.taraldsen
2017-05-03 7:15 ` Pete Heist
2017-05-03 10:03 ` Andy Furniss
2017-05-03 11:10 ` erik.taraldsen
2017-11-27 8:35 ` Dave Taht
2017-11-27 12:04 ` Jonathan Morton
2017-11-27 12:47 ` Pete Heist
2017-11-27 15:54 ` Sebastian Moeller
2017-11-27 16:12 ` Pete Heist
2017-11-27 18:28 ` Jonathan Morton
2017-11-27 21:49 ` Pete Heist
[not found] <mailman.1.1493827201.27042.cake@lists.bufferbloat.net>
2017-05-03 18:05 ` Pete Heist
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=1493789805885.56806@telenor.com \
--to=erik.taraldsen@telenor.com \
--cc=cake@lists.bufferbloat.net \
--cc=me@lochnair.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