546
edits
Performance Optimization Guide: Difference between revisions
→Skipped packets due to analyzer load imbalance
| Line 76: | Line 76: | ||
=== Skipped packets due to analyzer load imbalance === | === Skipped packets due to analyzer load imbalance === | ||
By default, the Allegro load balances the traffic between the analyzers based on the IP addresses of the client and server IP. This provides a very good balancing in most situations | By default, the Allegro load balances the traffic between the analyzers based on the IP addresses of the client and server IP. This provides a very good balancing in most situations. | ||
The load balancing behavior of the Allegro can be changed to flow load balancing mode at '''Settings''' -> '''Global Settings''' → '''Expert Settings'''. | The network packets cannot distributed equally among all analyzer threads if there are many connections between only few IP addresses. An example is 2 SIP trunks with many RTP connections. | ||
The load statistics will show parts of the analyzers with a constant high load and others with a significant lower load. | |||
The load balancing behavior of the '''Allegro Network Multimeter''' can be changed to flow based load balancing mode at '''Settings''' -> '''Global Settings''' → '''Expert Settings'''. | |||
[[File:Flow load balancing.png|600px]] | [[File:Flow load balancing.png|600px]] | ||
This mode improves the performance only for | This mode improves the performance only for imbalanced traffic. Use the option only if required as it has a negative performance impact on balanced traffic. | ||
== Database queues == | == Database queues == | ||