70
edits
Performance Optimization Guide: Difference between revisions
Jump to navigation
Jump to search
→Analyzer queues
(→Skipped packets at high analyzer load: Update dead wiki link) |
|||
| Line 40: | Line 40: | ||
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. | 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> | ||
<li>Utilization of individual analyzer threads: The load of the analyzer threads can be checked at the '''Info''' → '''System info''' → '''Load'''. Depending on the Allegro model there can be two (Allegro 200, Allegro 500) or up to 120 (Allegro 5300 or 5500) analyzer threads. | <li>Utilization of individual analyzer threads: The load of the analyzer threads can be checked at the '''Info''' → '''System info''' → '''Load'''. Depending on the Allegro model there can be two (Allegro 200, Allegro 500/510) 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. | 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> | </li> | ||