546
edits
Line 35: | Line 35: | ||
== Analyzer queues == | == Analyzer queues == | ||
The '''Allegro Network Multimeter''' has a packet queue between I/O threads and the analyzer threads which distributes the incoming packets to the actual processing threads. | The '''Allegro Network Multimeter''' has a packet queue between I/O threads and the analyzer threads which distributes the incoming packets to the actual processing threads. There are two statistics describing the load of the queues and analyzer threads. If analyzer threads cannot process incoming packets fast enough, the corresponding queue will eventually overflow and packets must be skipped for processing. | ||
<ol> | |||
<li>Graphs for skipped packets: You can check at the '''Interface stats''' per interface and check whether all I/O threads were able to push all packets to the analyzer queues or not. The corresponding counter is '''Not processed due to overload'''. | |||
[[File:Interface analyzer packet drop.png|400px]] | [[File:Interface analyzer packet drop.png|400px]] | ||
Please note that high counters for a few seconds at the initial startup of the device are normal when it is started under high network load scenarios. | |||
</li> | |||
<li>Utilization of individual analyzer threads: The load of the analyzer threads can be checked at the '''Info''' → '''System Info''' → '''Load'''. Depending of your Allegro model, there can be two (Allegro 200, Allegro 500) or up to 120 (Allegro 5300 or 5500) analyzer threads. | |||
The load graph gives an indication about the overall utilization of each thread but the important counter is the '''Not processed due to overload''' counter since this is the event when ultimately one or more packets could not be processed due to overload. | |||
</li> | |||
</ol> | |||
There are 3 scenarios where the a queue overload can happen, which are described in the following sections. | |||
There are 3 scenarios where the | |||
=== Overload at low analyzer load === | === Overload at low analyzer load === |
edits