1,775
edits
Feature documentation: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 26: | Line 26: | ||
* Queue multiplier: This setting configures the size of the message queue between packet analyzing threads and database threads. | * Queue multiplier: This setting configures the size of the message queue between packet analyzing threads and database threads. | ||
Usually the value does not need to be changed. If the system reports overload, the [[System_Info_Page|System Info Page]] should be checked. There is detailed | Usually the value does not need to be changed. If the system reports overload, the [[System_Info_Page|System Info Page]] should be checked. There is detailed load page when clicking on the load percentage. | ||
If any of packet analyzing threads show DB message lost counter, the queue size multiply might be increased. | If any of packet analyzing threads show DB message lost counter, the queue size multiply might be increased. | ||
| Line 33: | Line 33: | ||
Setting this value to 0 disables the DB mode. | Setting this value to 0 disables the DB mode. | ||
Depending on the complexity of the network traffic, it can be beneficial to increase or decrease the value. The default value on most system is 4 (if the DB mode is available). | Depending on the complexity of the network traffic, it can be beneficial to increase or decrease the value. The default value on most system is 4 (if the DB mode is available). | ||
The load graphs for each thread can be checked to decide if the value needs to be changed. | The [[System_Info_Page|load]] graphs for each thread can be checked to decide if the value needs to be changed. | ||
| Line 49: | Line 49: | ||
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 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. | ||
In this case it is beneficial to decrease the “DB thread factor” to use more DB threads and thus decrease the load per thread. | In this case it is beneficial to decrease the “DB thread factor” to use more DB threads and thus decrease the load per thread. | ||