Use the fastest connection based on session response. Fastest Response Time evolved from the Lowest Latency algorithm.
At the start of each session, traffic is duplicated and sent to all healthy connections. When the first response is received from a remote server, any further traffic for this session will be routed over that WAN connection for the fastest possible response time. If any slower responses are received on other connections afterwards, they will be discarded.
Common use case
Useful for time-sensitive applications such as online gaming.
What is the difference between the “lowest Latency” and “fastest Response” Outbound policy?
While the Lowest Latency algorithm gets the response from the second or third hop, the Fastest Response algorithm gets the response from the destination.
Another important difference is that the Lowest Latency Algorithm performs the check at a fixed interval, while the Fastest Response algorithm performs the check at the start of each session.
In most situations, the “Fastest Response Time” algorithm will provide the most accurate measurement.
However, there are two situations where you may still want to use “Lowest Latency”
- For sending traffic that does not require a response (i.e. single direction UDP Stream)
- For situations where bandwidth is limited, and duplication of packets is not allowed.