Event banner
Azure Load Testing AMA
Event Ended
Wednesday, Feb 22, 2023, 09:00 AM PSTEvent details
We are very excited to announce an Azure Load Testing AMA!
Azure Load Testing is a fully managed load-testing service built for Azure that makes it easy to generate high-scale load and identif...
EricStarker
Updated Feb 22, 2023
Joby_Jennings
Feb 22, 2023Occasional Reader
When configuring the load, you create more test engines to increase the threads above 250. Are the engines created in parallel or are they created one after the other? How do the multiple engines affect the ramp up time for the users? Do you have to increase the time in the JMeter script each time you want to increase the engine instances count?
Nitin_Joy
Microsoft
Feb 22, 2023Hi Joby_Jennings, all engine instances for a given load test run are created and configured in parallel. You wouldn't need to increase the test duration based on the number of engines, the test duration timer will be started only after all engines have started the test run.
Your JMeter script executes within the context of a single engine. So the ramp-up schedule is replicated for each engine.
To keep the overall ramp-up schedule the same, you'd need to factor in the number of VUsers that are being ramped up in accordance with the number of engines. You may also parameterize this field in the JMeter script to read from environment variables, so you wouldn't need to re-upload the script every time you need to change the number of engines and keep the ramp-up schedule the same.
You can find more information about parameterizing JMeter script here - Parameterize load tests with secrets and environment variables - Azure Load Testing | Microsoft Learn