From 523eea8b5c53e41aab45e17c22c816f3d2003f57 Mon Sep 17 00:00:00 2001 From: Rainer Gerhards Date: Fri, 11 Oct 2013 15:57:24 +0200 Subject: doc: describe new "thread" imudp module parameter --- doc/imudp.html | 9 +++++++++ 1 file changed, 9 insertions(+) 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. +
  • threads <number> (default 1), available since 7.5.5
    +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.

    Input Parameters: