We’re excited to share that mabl Link now supports performance tests!
Previously, running performance tests in private environments required allowlisting mabl static IP addresses, which wasn’t feasible for all teams. If technical constraints prevented your team from using static IP addresses, you now have the option to run performance tests over a mabl Link-enabled environment.
Running performance tests over mabl Link introduces additional steps to the path the test traffic takes, which may result in increased latency as measured by the performance test. For this reason, we recommend using the mabl Link approach primarily if the static IP address approach isn’t feasible for your team.
How it works
The process for running performance tests through mabl Link works just like it does for browser and API tests. To run a performance test that accesses resources in a private network, take the following steps:
- Start up the mabl Link Agent on a host within your network that has access to the application and resources under test
- Associate the Link Agent with the mabl environment where you’ve configured your private network
- Make sure your performance tests are configured to run over the Link-enabled environment
Concurrency limit
As we are evaluating this new functionality, our initial limit for performance runs over Link is 100 runners per performance test execution. If your performance test specifies more than 100 runners, we will automatically scale it down proportionately at execution time so that it does not exceed 100 when running over Link.
For example, if your performance test has 2 workloads, one with a concurrency of 50 and another with a concurrency of 100 (total 150), we will scale those down to 33 and 67, respectively, when you kick off the test. Running the same test in an environment that does not use Link will use the originally configured concurrency.