summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRainer Gerhards <rgerhards@adiscon.com>2013-10-11 15:57:24 +0200
committerRainer Gerhards <rgerhards@adiscon.com>2013-10-11 15:57:24 +0200
commit523eea8b5c53e41aab45e17c22c816f3d2003f57 (patch)
treecde1cb6df4b6d44451d3d57ae788c649805986ca
parent3f1fade3558f74e71233d51a14b1d0f1ae7716eb (diff)
downloadrsyslog-523eea8b5c53e41aab45e17c22c816f3d2003f57.tar.gz
rsyslog-523eea8b5c53e41aab45e17c22c816f3d2003f57.tar.bz2
rsyslog-523eea8b5c53e41aab45e17c22c816f3d2003f57.zip
doc: describe new "thread" imudp module parameter
-rw-r--r--doc/imudp.html9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/imudp.html b/doc/imudp.html
index 25a8d87a..1bd64a13 100644
--- a/doc/imudp.html
+++ b/doc/imudp.html
@@ -56,6 +56,15 @@ should not be overdone. For each buffer, max message size bytes are statically
required. Also, a too-high number leads to reduced efficiency, as some structures
need to be completely initialized before the OS call is done. We would suggest to not
set it above a value of 128, except if experimental results show that this is useful.
+<li><b>threads</b> &lt;number&gt; (default 1), available since 7.5.5<br>
+Number of worker threads to process incoming messages. These
+threads are utilized to pull data off the network. On a busy system, additional
+threads (but not more than there are CPUs/Cores) can help improving
+performance and avoiding message loss. Note that with too many threads, performance
+can suffer.
+There is a hard upper limit on the number of threads that can be defined.
+Currently, this limit is set to 32. It may increase in the future when massive
+multicore processors become available.
</ul>
<p><b>Input Parameters</b>:</p>
<ul>