The Sauce Labs Cookbook

Sauce Headless

Front End Performance Testing

Insights

External Resources

More Info


Page tree
Skip to end of metadata
Go to start of metadata

PAGE DEPRECATED: updated content available here.

Our High Availability Sauce Connect Proxy Setup enables you to configure multiple tunnels into tunnel pools, which are treated as a single tunnel. When running a tunnel pool, we recommend monitoring your activity in Tunnels to ensure your tunnel configuration stability and overall testing efficiency. Here, you can gain insight into all individual tunnels and tunnel pools. You can also check the health of an individual tunnel by running a test on it. 

Please be aware that each tunnel used in a pool will count toward your tunnel concurrency limit.

Failover and Rolling Restart Functionality

Because tunnel pools allow for failover and rolling restart functionality, this will improve Sauce Connect Proxy test stability and performance. Additionally, test load distribution is balanced automatically and evenly across tunnels using the round-robin load balancing method. This method accelerates test time and allow you to run a high volume of tests in parallel. 

Tunnel pools also abide by general fault tolerance rules. For example, if one tunnel becomes unavailable or shuts down (i.e., due to user shutdown, crash, maintenance, or network partition), you can configure your tunnels to be restored automatically while the test traffic is routed to another tunnel in the pool.

NOTE: Tunnel pools do not self-heal nor restart automatically. If a tunnel stops, you'll need to restart it manually. Other than restarting a stopped or failed tunnel, tunnel pools generally run automatically without user intervention. If you're running a high number of tunnels, you may want to bypass the pool and specify which tunnel to use directly.

Setup and Configuration for High Availability Mode

The key takeaway to remember when configuring tunnels to run in high availability mode is to use the --no-remove-colliding-tunnels flag. You must run this command on each machine where you want to have access to the tunnel pool.

See the following pages for more information: 

Implementing Tunnel Identifiers to Enable Monitoring

We recommend using tunnel identifiers to specify which tunnel in the pool you would like to use. You can view your full list of tunnel identifiers via Tunnels or by checking your Sauce Connect logs. See the following pages for more Information: