404
edits
Performance Optimization Guide: Difference between revisions
→High Level Allegro System Layout
No edit summary |
|||
| Line 14: | Line 14: | ||
* Disk I/O | * Disk I/O | ||
Please note that there are queues that buffer messages between all hardware instances ( | Please note that there are queues that buffer messages between all hardware instances ( Interface chips, central processing unit, storage ) and threads which can be tuned. The following queues can be monitored to see where you need to change settings in the Allegro: | ||
=== NIC Hardware Queue === | === NIC Hardware Queue === | ||
| Line 20: | Line 20: | ||
This first queue is between the Network card and processing unit. Whenever the I/O threads are too slow to consume all packets from the built-in or extension ports, the '''hardware miss''' counter of the interface statistics will increase over time. | This first queue is between the Network card and processing unit. Whenever the I/O threads are too slow to consume all packets from the built-in or extension ports, the '''hardware miss''' counter of the interface statistics will increase over time. | ||
The load of the I/O threads can be checked at the '''Info''' → '''System Info''' → '''Load'''. | The load of the I/O threads can be checked at the '''Info''' → '''System Info''' → '''Load'''. | ||
If this counter increases regularly, you can try the following settings: | If this counter increases regularly, you can try the following settings: | ||
| Line 27: | Line 27: | ||
* increase the number of I/O threads: [[#More I/O Threads]] | * increase the number of I/O threads: [[#More I/O Threads]] | ||
=== Analyzer | === Analyzer queue === | ||
The Allegro has a packet queue between I/O threads and the analyzer threads. | The Allegro has a packet queue between I/O threads and the analyzer threads. There are 3 scenarios where the an queue overload can happen. | ||
==== Low analyzer load and drop ==== | |||
This happens if the Allegro is in a powersafe mode and a sudden peak of traffic is monitored. The solution is to use the [[#Sink Mode]] and to activate the '''Analyzer queue overcommit''' at '''Settings''' → '''Global settings''' → '''Expert settings'''. This allows to buffer sudden network bursts. | |||
[[File:Queue overcommit.png|600px]] | |||
==== High analyzer load ==== | |||
==== not-balanced Analyzer load ==== | |||
Please note that the increasing counters at the initial startup of the Allegro can be normal under high load scenarios for a few seconds. | Please note that the increasing counters at the initial startup of the Allegro can be normal under high load scenarios for a few seconds. | ||
=== DB Queue === | === DB Queue === | ||
== Packet Drops in Queue == | == Packet Drops in Queue == | ||