From 6b26674e2673fab35072fa2df1789cf7f7b9fe5e Mon Sep 17 00:00:00 2001 From: Kolbe Kegel Date: Wed, 4 Feb 2015 15:54:56 -0800 Subject: [PATCH] Configuration-Guide.md --- Documentation/Getting-Started/Configuration-Guide.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation/Getting-Started/Configuration-Guide.md b/Documentation/Getting-Started/Configuration-Guide.md index 372611eea..9ef4b0ad0 100644 --- a/Documentation/Getting-Started/Configuration-Guide.md +++ b/Documentation/Getting-Started/Configuration-Guide.md @@ -82,6 +82,7 @@ The global settings, in a section named `[MaxScale]`, allow various parameters t To control the number of threads that poll for network traffic set the parameter threads to a number. It is recommended that you start with a single thread and add more as you find the performance is not satisfactory. MaxScale is implemented to be very thread efficient, so a small number of threads is usually adequate to support reasonably heavy workloads. Adding more threads may not improve performance and can consume resources needlessly. +``` \# Valid options are: \# threads= @@ -89,6 +90,7 @@ To control the number of threads that poll for network traffic set the parameter [MaxScale] threads=1 +``` It should be noted that additional threads will be created to execute other internal services within MaxScale, this setting is merely used to configure the number of threads that will be used to manage the user connections.