--- suricata.yaml	2010-07-21 14:51:45.000000000 -0500
+++ suricata-high.yaml	2010-07-21 15:12:30.000000000 -0500
@@ -8,7 +8,7 @@
 # If you are using the CUDA pattern matcher (b2g_cuda below), different rules
 # apply. In that case try something like 4000 or more. This is because the CUDA
 # pattern matcher scans many packets in parallel.
-#max-pending-packets: 50
+max-pending-packets: 5000
 
 # Set the order of alerts bassed on actions
 # The default order is pass, drop, reject, alert
@@ -89,7 +89,7 @@
 # make sure to define the values at "- custom-values" as your convenience.
 # Usually you would prefer medium/high/low
 detect-engine:
-  - profile: medium
+  - profile: high 
   - custom-values:
       toclient_src_groups: 2
       toclient_dst_groups: 2
@@ -118,7 +118,7 @@
   # 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.5 
 
 # Select the cuda device to use.  The device_id identifies the device to be used
 # if one has multiple devices on the system.  To find out device_id associated
@@ -185,9 +185,9 @@
 # not in use.
 
 flow:
-  memcap: 33554432
-  hash_size: 65536
-  prealloc: 10000
+  memcap: 134217728 
+  hash_size: 262144 
+  prealloc: 40000
   emergency_recovery: 30
   prune_flows: 5
 
@@ -247,9 +247,11 @@
 #     memcap: 67108864          # 64mb tcp reassembly memcap
 #     depth: 1048576            # 1 MB reassembly depth
 stream:
-  memcap: 33554432
+  memcap: 268435456
+  max_sessions: 1048576
+  prealloc_sessions: 65536 
   reassembly:
-    memcap: 67108864
+    memcap: 268435456
     depth: 1048576
 
 # Logging configuration.  This is not about logging IDS alerts, but