Performance Optimization Guide: Difference between revisions

Line 39: Line 39:
==== High analyzer load ====
==== High analyzer load ====


There are a few options for reducing the analyzer load but it always comes with the penalty of not processing all data.
There are a few options for reducing the analyzer load but it always comes with the penalty of not processing all data. You can '''reduce''' the statistic level or add a '''NIC filter'''.
 
===== Reducing statistic level =====


You can reduce the level of analysis at '''Settings''' -> '''Global Settings'''.
You can reduce the level of analysis at '''Settings''' -> '''Global Settings'''.
Line 47: Line 45:
[[File:Detail of traffic analysis.png|600px]]
[[File:Detail of traffic analysis.png|600px]]


Every Level reduction will reduce the amount of analyzed data and saves database operations. You can use this mode to store high packet rates into the ring buffer and re-analyze parts of it with full analytics with the [[[Parallel packet processing]].
Every Level reduction will reduce the amount of analyzed data and saves database operations, see [[Global_settings#Limit_module_processing]] for more details of this mode. You can use this mode to store high packet rates into the ring buffer and re-analyze parts of it with full analytics with the [[[Parallel packet processing]].
 
The NIC filter can be used to reduce the amount of monitored traffic. It excludes traffic from the analyzers for the cost of not-seeing all traffic of the link. See the [[Filter|Nic Filter]] for more details.


==== not-balanced Analyzer load ====
==== not-balanced Analyzer load ====
404

edits