1,775
edits
No edit summary |
No edit summary |
||
Line 33: | Line 33: | ||
Depending on the actual network, there can be situations where different configuration settings lead to better overall performance. | Depending on the actual network, there can be situations where different configuration settings lead to better overall performance. | ||
1.System overload and skipped packets. | 1. System overload and skipped packets. | ||
:If packet drops appear, the packet analyzing threads might be overloaded. This can be checked in the load statistics. | :If packet drops appear, the packet analyzing threads might be overloaded. This can be checked in the load statistics. | ||
:The current load percentage can be clicked to get detailed information about each system component. If the analyzing threads tend to have significantly more load than the DB threads, it is recommended to increase the '''DB thread factor''' in allocate less DB threads and use more analyzing threads. | :The current load percentage can be clicked to get detailed information about each system component. If the analyzing threads tend to have significantly more load than the DB threads, it is recommended to increase the '''DB thread factor''' in allocate less DB threads and use more analyzing threads. | ||
2.System overload due to DB message lost. | 2. System overload due to DB message lost. | ||
:If DB message lost counters appear in the detailed [[System_Info_Page|load]] statistics (by clicking on the current load percentage), it means that the DB threads where not capable of processing the data created by the analyzing threads. | :If DB message lost counters appear in the detailed [[System_Info_Page|load]] statistics (by clicking on the current load percentage), it means that the DB threads where not capable of processing the data created by the analyzing threads. | ||
edits