DLT

[dileepreddygaddam]

I'm trying to create a JMeter .jmx test plan with multiple Thread Groups, each targeting different API endpoints and configured with different load profiles. I've set startup delays for each Thread Group (e.g., Thread_1 = 0s, Thread_2 = 120s, Thread_3 = 240s) so they execute sequentially. This setup works correctly in my local environment, but when I run it in Distributed Load Testing (DLT), all Thread Groups start simultaneously and the startup delays are ignored. Can anyone advise on how to properly design this scenario for DLT?

[shujacks]

Thanks for reaching out. We are looking into this and will respond shortly.

[JimTharioAmazon]

Hi, DLT will ignore the timing settings inside the .jmx file and use the timing information set in the DLT scenario data. You mention you want to run these tests sequentially. Have you tried setting these up sequentially in the same ThreadGroup one after the next, or do you you a need for these to be in separate ThreadGroups?

[dileepreddygaddam]

Yes, we would like them to be placed in separate Thread Groups so that we can simulate different load conditions for each group. Please let us know what changes are required to achieve this. Thank you!

[JimTharioAmazon]

Have you been able to see if the delayed threadgroups work if only one task is launched? We may have a case where the Taurus wrapper is ignoring those JMeter timing settings. I am looking at that. Another suggestion, which is not the best case, is trying to launch these as separate scheduled tests. Since we're looking for workarounds, I'll also add this to a backlog.

[dileepreddygaddam]

Currently, delayed Thread Groups are being ignored even when they contain a single task. Yes, we are running them separately with different throughput, we would prefer to combine them into a single test plan to simplify report consolidation, which is becoming increasingly difficult. Thank you!

[JimTharioAmazon]

We're going to work on a fix for this following our upcoming release in a few weeks. It looks like we may need to make changes to how the Taurus wrapper is using the timing information from the .jmx and any timing information sent in from the DLT application.