546
edits
Performance Optimization Guide: Difference between revisions
→Overload and not-balanced analyzer load
| Line 74: | Line 74: | ||
[[File:Queue overcommit.png|600px]] | [[File:Queue overcommit.png|600px]] | ||
=== | === 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. The load distribution could be not balanced if there are many connections and load between 2 IP addresses. An example are 2 SIP trunks with many RTP connections. The statistics will show a part of the analyzers with a constant high load and others with a significant lower load. | 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 distribution could be not balanced if there are many connections and load between 2 IP addresses. An example are 2 SIP trunks with many RTP connections. The statistics will show a part of the analyzers with a constant high load and others with a significant lower load. | ||