From: Victor Julien <victor@inliniac.net>
Date: Fri, 3 Jun 2016 08:53:46 +0000 (+0200)
Subject: yaml: improve affinity defaults
X-Git-Tag: suricata-3.1RC1~11
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=0b6171854dcf6fc431860c80d2e99dd69f6df60c;p=thirdparty%2Fsuricata.git

yaml: improve affinity defaults
---

diff --git a/suricata.yaml.in b/suricata.yaml.in
index 6caadc84b3..a1cacd48c8 100644
--- a/suricata.yaml.in
+++ b/suricata.yaml.in
@@ -1292,10 +1292,10 @@ threading:
           medium: [ "1-2" ]
           high: [ 3 ]
           default: "medium"
-    - verdict-cpu-set:
-        cpu: [ 0 ]
-        prio:
-          default: "high"
+    #- verdict-cpu-set:
+    #    cpu: [ 0 ]
+    #    prio:
+    #      default: "high"
   #
   # By default Suricata creates one "detect" thread per available CPU/CPU core.
   # This setting allows controlling this behaviour. A ratio setting of 2 will
@@ -1305,7 +1305,7 @@ threading:
   # thread being created. Regardless of the setting at a minimum 1 detect
   # thread will always be created.
   #
-  detect-thread-ratio: 1.5
+  detect-thread-ratio: 1.0
 
 # Profiling settings. Only effective if Suricata has been built with the
 # the --enable-profiling configure flag.