404
edits
Performance Optimization Guide: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
* I/O Threads: responsible for all packet I/O operations | * I/O Threads: responsible for all packet I/O operations | ||
* Analyzer Threads: responsible for decoding | * Analyzer Threads: responsible for decoding and most of the DB operations | ||
* DB Threads: optional threads offloading memory intensive database operations, see [[DB mode]] | * DB Threads: optional threads offloading memory intensive database operations, see [[DB mode]] | ||
* | |||
Please note that there are queues that buffer messages between all hardware instances ( NICs, Storage ) and Threads which can be optimized. By default, the Allegro runs in a configuration that fits for the majority of users. | |||
== Packet Drops in Queue == | |||
The Allegro Network Multimeter will inform you if a packet loss has been happened. The Allegro has certain hardware and software queues that can drop packet due overload. | |||
== Generic Optimizations == | == Generic Optimizations == | ||
== Packet Processing: Bridge vs. Sink Mode == | |||
=== Packet Processing: Bridge vs. Sink Mode === | |||
For configuration, please see: [[Global_settings#Packet_processing_mode]] | For configuration, please see: [[Global_settings#Packet_processing_mode]] | ||
The bridge mode requires approximately 10 % more load on the I/O Threads | The bridge mode requires approximately 10 % more load on the I/O Threads as this threads have to sent the traffic to the corresponding network interface for forwarding. Allegro recommends to use | ||
=== More I/O Threads === | |||
== Specific Optimizations == | == Specific Optimizations == | ||