Performance Optimization Guide: Difference between revisions

no edit summary
No edit summary
Line 24: Line 24:
TODO: add overloaded Interface graph.
TODO: add overloaded Interface graph.


If this counter increases regularly, you can try the following settings:
If this counter increases regularly, you can try to use the sink mode and to increase the number of I/O threads.


* use sink mode instead of bridge mode, see below [[#Sink Mode]]
The bridge mode requires approximately 10 - 30 % more load on the I/O Threads as the sink mode. The I/O threads have to sent the traffic to the corresponding network interface for forwarding.
For configuration, please see: [[Global_settings#Packet_processing_mode]]
 
The number of I/O threads can be increased at the cost of analyzer threads.
TODO...
* increase the number of I/O threads: [[#More I/O Threads]]
* increase the number of I/O threads: [[#More I/O Threads]]


Line 70: Line 74:


If enabled, you can check if there are message drops between the analyzer threads and the DB threads in the load statistics.
If enabled, you can check if there are message drops between the analyzer threads and the DB threads in the load statistics.
== 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.
== Optimizations ==
=== Sink Mode ===
For configuration, please see: [[Global_settings#Packet_processing_mode]]
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 ==
404

edits