Latency-based load balancing performs similarly to Round Robin or Weighted Round Robin, but also accounts for round trip time (RTT) and is configured using Record Pools. With this approach, end users are always pointed to the best-performing endpoint. Endpoints are monitored through Sonar, which checks the health of each resource in your pool.
Visit our blog to learn more about ITO Latency Load Balancing.
This load-balancing solution is ideal for multi-vendor configurations like Multi-CDN or multi-cloud environments. Dynamically serve end users based on geographic location and how fast resources respond by creating ITO record pools consisting of multiple IP addresses or hostnames.
Before you can enable ITO for record pools, you need to create Sonar monitoring checks. The following steps will walk you through the entire process.
If you do not have a record pool configured for your domain yet, you will need to create one now by following the steps below. In this example, we will be using A Records, but the same steps apply to AAAA, ANAME, and CNAME records.
If you already have a pool set up that you want to enable ITO for, skip to step 4, option D.
A. Name: Give your pool configuration an identifiable name.
B. Num Return: Specify the number of IPs you want to have returned in the pool.
C. Min Available: Enter the minimum number of IPs that must be available in the pool.
D. Enable ITO: Tick the checkbox to enable ITO for your pool.
E. Monitoring Frequency: Choose the frequency that you want the IPs in your pool to be checked.
F. Use Best Performing: Enter the number of returned endpoints you want to be optimized by ITO.
G: Monitoring Region: Choose the monitoring region for your pool. You should have selected multiple monitoring locations for this region in your Sonar check.
H: Deviation Allowance: This option allows you to choose which endpoints are in the pool based on performance deviations.
I: Performance Handicap: Choose whether you want your returned IPs to be adjusted by percentage, speed, or none.
J. Contact Notify: This option allows you to select a contact list to send notifications to. For help setting up a contact list, go here.
K. IP: Enter the IPv4 address you are pointing to.
L. Weight: You can distribute weight equally between IPs in a pool, or choose a different weight for each IP, depending on how you want to optimize your traffic. A higher weight will send more traffic to that IP. See our Weighted Round Robin tutorial to learn more.
M. Sonar Check: If you set Policy (see step I. below) to "Follow Sonar" or "Off on Failure," click in the “Sonar Check” field and select the desired Sonar Check from the drop-down text box.
N. Policy: There are four policies. Follow Sonar is recommended for ITO pools in most cases, but you can choose the policy that best fits the specific needs of your domain:
O. Add Another IP: You will need to click this option for each additional IP you want to add to the record pool.
You can also combine ITO latency-based load balancing with GeoDNS.
Visit our website for more information on our services and features.