FatPipe provides four methods of load balancing: Round Robin, Response Time, Fastest Route, and Weighted. To configure a specific load balancing algorithm, click on the Load Balancing button listed in the main menu and click the Algorithms tab
Configures FatPipe to send sessions down the lines in rotating order. This method is recommended for similar speed connections to the Internet, even if the connections are not of the same ISP (e.g., combining two similar speed fractional T1s and a DSL line).
Configures FatPipe to balance traffic based on each line’s average response time for Internet requests. This method is recommended for unequal speed connections. The fastest line will be used more often with Response Time.
Configures FatPipe to balance traffic on a per-destination basis. Each session will go over the fastest line for its destination. Choose this option when you want to make sure each session goes out the line with the fastest route for its destination. (There is slight overhead with this algorithm since SYN packets get sent out on all lines at the start of each session).
Algorithm configures FatPipe to balance traffic in proportion to the WAN weights defined by you. Each interface needs to be assigned a weight. (Default value for each interface is 1.) The ratio of these weights determines the ratio of downloaded traffic on the respective Internet lines, which the load balancing algorithm maintains.
For example, if weights for WAN1, WAN2, WAN3 are 1, 2, 3, respectively, and total download traffic amounts to 600kbps, the traffic will be balanced over respective lines as 100, 200, 300 kbps. Because FatPipe MPVPN balances sessions rather than packets, real world results will rarely achieve this ideal. In general, the greater the number of sessions, the closer the distribution of traffic will be to the specified weights.