commit 8368f6d47199834e6ca005a8c0f4a242161c0ccb
parent 6bfeb8e037247287c543e9f1338c863189db10c1
Author: Joris Vink <joris@coders.se>
Date: Sun, 20 Dec 2015 11:21:40 +0100
Updated comment section on worker_accept_threshold.
Diffstat:
conf/kore.conf.example | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/conf/kore.conf.example b/conf/kore.conf.example
@@ -34,9 +34,14 @@ workers 4
#worker_rlimit_nofiles 1024
# Limit the number of new connections a worker can accept
-# in a single event loop.
-# NOTE: This can have a *MASSIVE* impact as this controls
-# how new connections are spread across worker processes.
+# in a single event loop. By default Kore will accept as
+# many new connections it can up to worker_max_connections.
+#
+# NOTE: If you are running benchmark tools that throw all
+# connections at Kore at the same time (when they are less
+# then worker_max_connections) or you have an actual reason
+# to not spend too much time in the accept loop this setting
+# will make a HUGE positive difference.
#
# This is disabled by default. If you wish to enable this
# specify the number of connections a worker will accept