325
edits
Performance Optimization Guide: Difference between revisions
Performance Optimization Guide (view source)
Revision as of 09:52, 9 December 2020
, 9 December 2020no edit summary
Remco.derooy (talk | contribs) |
Remco.derooy (talk | contribs) No edit summary |
||
| Line 25: | Line 25: | ||
If the load is near 100%, packet loss can occur and the following countermeasures can be attempted: | If the load is near 100%, packet loss can occur and the following countermeasures can be attempted: | ||
# The Bridge mode requires approximately 10% - 30% more load on the I/O threads than the Sink mode. The I/O threads have to | # The Bridge mode requires approximately 10% - 30% more load on the I/O threads than the Sink mode. The I/O threads have to send the incoming traffic to the corresponding outgoing network interface for forwarding. If packet forwarding is not necessary (for example when being deployed at a Mirror Port), switching to '''Sink mode''' will improve the performance of the device. For configuration, please see [[Global_settings#Packet_processing_mode|Global settings]]. | ||
# The number of queues can be adjusted at the cost of analyzer threads. Each queue uses a corresponding CPU thread so more queues means less CPU threads available for other components. This option is available on the Allegro 3000 and above due to the large number of internal CPU cores. Allegro Packets recommends to increase the number of queues only on the Allegro 3000 and above if necessary. | # The number of queues can be adjusted at the cost of analyzer threads. Each queue uses a corresponding CPU thread so more queues means less CPU threads available for other components. This option is available on the Allegro 3000 and above due to the large number of internal CPU cores. Allegro Packets recommends to increase the number of queues only on the Allegro 3000 and above if necessary. | ||
:: This setting can be changed at '''Settings''' -> '''Global settings''' → '''Expert settings''' | :: This setting can be changed at '''Settings''' -> '''Global settings''' → '''Expert settings''' | ||
| Line 64: | Line 64: | ||
=== Skipped packets at low analyzer load === | === Skipped packets at low analyzer load === | ||
The '''Allegro Network Multimeter''' conserves energy in very low traffic situations. Large packet bursts can lead to a high traffic situation so the | The '''Allegro Network Multimeter''' conserves energy in very low traffic situations. Large packet bursts can lead to a high traffic situation so the analyzer threads cannot keep up with the incoming packets fast enough during the period of power adjustment. After that small period of time, the analyzer threads are again fast enough to process the traffic. | ||
This can be identified if packets are not processed while the system load is still not very high at the same time. | This can be identified if packets are not processed while the system load is still not very high at the same time. | ||
If this occurs, the option '''Analyzer queue overcommit''' at '''Settings''' → '''Global settings''' → '''Expert settings''' can be enabled. It increases the queue size to be able to buffer network | If this occurs, the option '''Analyzer queue overcommit''' at '''Settings''' → '''Global settings''' → '''Expert settings''' can be enabled. It increases the queue size to be able to buffer network bursts during a short time period. The disadvantage is that the queues are overcommitted so it can happen that the network card does not have enough buffers available for incoming packets so some packets may not be forwarded in bridge. Therefore, this option is only recommended in '''Sink mode'''. | ||
[[File:Queue overcommit.png|600px]] | [[File:Queue overcommit.png|600px]] | ||