DOC: typo: maxconn paragraph is wrong due to a wrong buffer size

HAProxy allocates 2 tune.bufsize, which is by default 16kB.

backport: 1.4 and above

diff --git a/doc/configuration.txt b/doc/configuration.txt
index d54459a0aa61b19e26d47e74d71ba87a051e74bf..5dbcafe2ff26dc52d1fe6b28702c7e4c811fea1c 100644 (file)
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -4560,10 +4560,10 @@ maxconn <conns>
   very high so that haproxy manages connection queues, instead of leaving the
   clients with unanswered connection attempts. This value should not exceed the
   global maxconn. Also, keep in mind that a connection contains two buffers
-  of 8kB each, as well as some other data resulting in about 17 kB of RAM being
-  consumed per established connection. That means that a medium system equipped
-  with 1GB of RAM can withstand around 40000-50000 concurrent connections if
-  properly tuned.
+  of tune.bufsize (16kB by default) each, as well as some other data resulting
+  in about 33 kB of RAM being consumed per established connection. That means
+  that a medium system equipped with 1GB of RAM can withstand around
+  20000-25000 concurrent connections if properly tuned.
 
   Also, when <conns> is set to large values, it is possible that the servers
   are not sized to accept such loads, and for this reason it is generally wise