22<html lang="en">
33 <head>
44 <meta charset="utf-8" />
5- <title>HAProxy version 3.1-dev13-100 - Configuration Manual</title>
5+ <title>HAProxy version 3.1-dev14 - Configuration Manual</title>
66 <link href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/css/bootstrap.min.css" rel="stylesheet" />
77 <link href="https://raw.githubusercontent.com/thomaspark/bootswatch/v3.3.7/cerulean/bootstrap.min.css" rel="stylesheet" />
88 <link href="../css/page.css?0.4.2-15" rel="stylesheet" />
44244424 You can use <strong>left</strong> and <strong>right</strong> arrow keys to navigate between chapters.<br>
44254425 </p>
44264426 <p class="text-right">
4427- <small>Converted with <a href="https://github.com/cbonte/haproxy-dconv">haproxy-dconv</a> v<b>0.4.2-15</b> on <b>2024/11/20 </b></small>
4427+ <small>Converted with <a href="https://github.com/cbonte/haproxy-dconv">haproxy-dconv</a> v<b>0.4.2-15</b> on <b>2024/11/21 </b></small>
44284428 </p>
44294429 </div>
44304430 <!-- /.sidebar -->
44354435 <div class="text-center">
44364436 <h1><a href="http://www.haproxy.org/" title="HAProxy"><img src="../img/HAProxyCommunityEdition_60px.png?0.4.2-15" /></a></h1>
44374437 <h2>Configuration Manual</h2>
4438- <p><strong>version 3.1-dev13-100 </strong></p>
4438+ <p><strong>version 3.1-dev14 </strong></p>
44394439 <p>
4440- 2024/11/15 <br>
4440+ 2024/11/21 <br>
44414441
44424442 </p>
44434443 </div>
@@ -6528,7 +6528,7 @@ <h2 id="chapter-2.3" data-target="2.3"><small><a class="small" href="#2.3">2.3.<
65286528 | HAPROXY_MWORKER | X | | | | | X | X |
65296529 | HAPROXY_CLI | | | | | | | X |
65306530 | HAPROXY_MASTER_CLI | | | | | | X | |
6531- | HAPROXY_LOCALPEER | | | | | | | X |
6531+ | HAPROXY_LOCALPEER | | | X | | | | X |
65326532 | HAPROXY_HTTP_LOG_FMT | | | X | | X | | |
65336533 | HAPROXY_HTTP_CLF_LOG_FMT | | | X | | X | | |
65346534 | HAPROXY_HTTPS_LOG_FMT | | | X | | X | | |
@@ -21297,31 +21297,32 @@ <h2 id="chapter-5.1" data-target="5.1"><small><a class="small" href="#5.1">5.1.<
2129721297protocol for all connections instantiated from this listening socket. For
2129821298instance, it is possible to force the http/2 on clear TCP by specifying "proto
2129921299h2" on the bind line.
21300- </pre><a class="anchor" name="quic-cc-algo"></a><a class="anchor" name="5-quic-cc-algo"></a><a class="anchor" name="5.1-quic-cc-algo"></a><a class="anchor" name="quic-cc-algo (Bind and server options)"></a><a class="anchor" name="quic-cc-algo (Bind options)"></a><div class="keyword"><b><a class="anchor" name="quic-cc-algo"></a><a href="#5.1-quic-cc-algo">quic-cc-algo</a></b> <span style="color: #800">{ cubic
<span style="color: #008">[-pacing]</span> | newreno | bbr | nocc }</span><span style="color: #008">[(<span style="color: #080"><args,...></span>)]</span></div><pre class="text">This is a QUIC specific setting to select the congestion control algorithm
21300+ </pre><a class="anchor" name="quic-cc-algo"></a><a class="anchor" name="5-quic-cc-algo"></a><a class="anchor" name="5.1-quic-cc-algo"></a><a class="anchor" name="quic-cc-algo (Bind and server options)"></a><a class="anchor" name="quic-cc-algo (Bind options)"></a><div class="keyword"><b><a class="anchor" name="quic-cc-algo"></a><a href="#5.1-quic-cc-algo">quic-cc-algo</a></b> <span style="color: #800">{ cubic | newreno | bbr | nocc }</span><span style="color: #008">[(<span style="color: #080"><args,...></span>)]</span></div><pre class="text">This is a QUIC specific setting to select the congestion control algorithm
2130121301for any connection attempts to the configured QUIC listeners. They are similar
2130221302to those used by TCP.
2130321303
2130421304Default value: cubic
2130521305
2130621306It is possible to active pacing if the algorithm is compatible. This is done
21307- by using the suffix "-pacing" after the algorithm name. Pacing purpose is to
21308- smooth emission of data without burst to reduce network loss. In some
21309- scenario, it can significantly improve network throughput. However, it can
21310- also increase CPU usage if haproxy is forced to wait too long between each
21311- emission. Pacing support is still experimental, as such it requires
21312- "<a href="#expose-experimental-directives">expose-experimental-directives</a>". BBR congestion control algorithm depends on
21313- the pacing support which is in this case implicitely activated by "bbr".
21314- Note that BBR haproxy implementation is still considered as experimental and
21315- cannot be enabled without "<a href="#expose-experimental-directives">expose-experimental-directives</a>".
21307+ by specifying optional burst argument as described in the next paragraph.
21308+ Pacing purpose is to smooth emission of data without burst to reduce network
21309+ loss. In some scenario, it can significantly improve network throughput.
21310+ However, it can also increase CPU usage if haproxy is forced to wait too long
21311+ between each emission. Pacing support is still experimental, as such it
21312+ requires "<a href="#expose-experimental-directives">expose-experimental-directives</a>". BBR congestion control algorithm
21313+ depends on the pacing support which is in this case implicitely activated by
21314+ "bbr". Note that BBR haproxy implementation is still considered as
21315+ experimental and cannot be enabled without "<a href="#expose-experimental-directives">expose-experimental-directives</a>".
2131621316
2131721317For further customization, a list of parameters can be specified after the
2131821318algorithm token. It must be written between parenthesis, separated by a comma
2131921319operator. Each argument is optional and can be empty if needed. Here is the
2132021320mandatory order of each parameters :
2132121321- maximum window size in bytes. It must be greater than 10k and smaller than
2132221322 4g. By default "<a href="#tune.quic.frontend.default-max-window-size">tune.quic.frontend.default-max-window-size</a>" value is used.
21323- - count of datagrams to emit in a burst if pacing is activated. It must be
21324- between the default value of 1 and 1024.
21323+ - burst size in bytes. By default, it is set to 0, which means unlimited. A
21324+ positive value up to 1024 can be specified to smooth emission with pacing.
21325+ See above paragraph for more explanation.
2132521326</pre><div class="separator">
2132621327<span class="label label-success">Example:</span>
2132721328<pre class="prettyprint">
@@ -21330,7 +21331,7 @@ <h2 id="chapter-5.1" data-target="5.1"><small><a class="small" href="#5.1">5.1.<
2133021331<span class="comment"># cubic congestion control algorithm with one megabytes as window</span>
2133121332quic-cc-algo cubic(1m)
2133221333<span class="comment"># cubic with pacing on top of it, with burst limited to 12 datagrams</span>
21333- quic-cc-algo cubic-pacing (,12)
21334+ quic-cc-algo cubic(,12)
2133421335</code></pre>
2133521336</div><pre class="text">A special value "nocc" may be used to force a fixed congestion window always
2133621337set at the maximum size. It is reserved for debugging scenarios to remove any
@@ -31687,8 +31688,8 @@ <h2 id="chapter-11.3" data-target="11.3"><small><a class="small" href="#11.3">11
3168731688 <br>
3168831689 <hr>
3168931690 <div class="text-right">
31690- HAProxy 3.1-dev13-100 – Configuration Manual<br>
31691- <small>, 2024/11/15 </small>
31691+ HAProxy 3.1-dev14 – Configuration Manual<br>
31692+ <small>, 2024/11/21 </small>
3169231693 </div>
3169331694 </div>
3169431695 <!-- /.col-lg-12 -->
0 commit comments