404
edits
Performance Optimization Guide: Difference between revisions
→Not-balanced analyzer load
No edit summary |
|||
| Line 59: | Line 59: | ||
==== Not-balanced analyzer load ==== | ==== Not-balanced analyzer load ==== | ||
By default, the Allegro load balances the traffic between the analyzers based on the IP addresses of the client and server IP. 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. This can be improved by using the flow load balancing mode at '''Settings''' -> '''Global Settings''' → '''Expert Settings'''. | 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. This can be improved by using the flow 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 unbalanced traffic. Please use it only if required as it has a negative performance impact on balanced traffic. | |||
=== DB Queue === | === DB Queue === | ||