summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Micay <danielmicay@gmail.com>2021-01-01 00:54:31 -0500
committerDaniel Micay <danielmicay@gmail.com>2021-01-01 00:54:31 -0500
commit826ad3fd6b91cdeaced9c2886f9e2d60c694465d (patch)
treeccec096d5bdfe27cd266abd1f795dc70aa0b79bb
parenta1695e62adf65daab005aa58a852c528d336f230 (diff)
clarify server traffic shaping future section
-rw-r--r--static/articles/server-traffic-shaping.html13
1 files changed, 7 insertions, 6 deletions
diff --git a/static/articles/server-traffic-shaping.html b/static/articles/server-traffic-shaping.html
index aa2c4ff8..74df9cd1 100644
--- a/static/articles/server-traffic-shaping.html
+++ b/static/articles/server-traffic-shaping.html
@@ -199,12 +199,13 @@
<section id="future">
<h2><a href="#future">Future</a></h2>
- <p>Ideally, data centers would deploy CAKE within their networks. This may mean
- they need to use more powerful hardware for routing. If the natural bottlenecks
- used CAKE, setting up traffic shaping on the server wouldn't be necessary. This
- doesn't seem likely any time soon. Deploying <code>fq_codel</code> is much more
- realistic and tackles buffer bloat but not the issue of fairness between hosts
- rather than only streams.</p>
+ <p>Ideally, data centers would deploy CAKE throughout their networks with the
+ default <code>triple-isolate</code> flow isolation. This may mean they need to use
+ more powerful hardware for routing. If the natural bottlenecks used CAKE, setting
+ up traffic shaping on the server wouldn't be necessary. This doesn't seem likely
+ any time soon. Deploying <code>fq_codel</code> is much more realistic and tackles
+ buffer bloat but not the issue of fairness between hosts rather than only
+ streams.</p>
</section>
</main>
<footer>