546
edits
Performance Optimization Guide: Difference between revisions
→Interface hardware queues
No edit summary |
|||
| Line 28: | Line 28: | ||
# The bridge mode requires approximately 10% - 30% more load on the I/O threads than the sink mode. The I/O threads have to sent 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 bridge mode requires approximately 10% - 30% more load on the I/O threads than the sink mode. The I/O threads have to sent 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 | # 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''' | |||
:: [[File:Rx sockets io thread.png|600px]] | |||
:: Allegro Packets recommends to test with HT enabled and 2 or 4 queue for I/O. If you disable the load on the analyzers (see [[#High analyzer load]]), you can also test with 4 queues (I/O Threads) without HT for maximum performance. | |||
== Analyzer queues == | == Analyzer queues == | ||