clarify server traffic shaping future section
This commit is contained in:
parent
a1695e62ad
commit
826ad3fd6b
@ -199,12 +199,13 @@
|
|||||||
<section id="future">
|
<section id="future">
|
||||||
<h2><a href="#future">Future</a></h2>
|
<h2><a href="#future">Future</a></h2>
|
||||||
|
|
||||||
<p>Ideally, data centers would deploy CAKE within their networks. This may mean
|
<p>Ideally, data centers would deploy CAKE throughout their networks with the
|
||||||
they need to use more powerful hardware for routing. If the natural bottlenecks
|
default <code>triple-isolate</code> flow isolation. This may mean they need to use
|
||||||
used CAKE, setting up traffic shaping on the server wouldn't be necessary. This
|
more powerful hardware for routing. If the natural bottlenecks used CAKE, setting
|
||||||
doesn't seem likely any time soon. Deploying <code>fq_codel</code> is much more
|
up traffic shaping on the server wouldn't be necessary. This doesn't seem likely
|
||||||
realistic and tackles buffer bloat but not the issue of fairness between hosts
|
any time soon. Deploying <code>fq_codel</code> is much more realistic and tackles
|
||||||
rather than only streams.</p>
|
buffer bloat but not the issue of fairness between hosts rather than only
|
||||||
|
streams.</p>
|
||||||
</section>
|
</section>
|
||||||
</main>
|
</main>
|
||||||
<footer>
|
<footer>
|
||||||
|
Loading…
x
Reference in New Issue
Block a user