Hello,
We currently identified this bugzilla few time ago :

   - https://bz.apache.org/bugzilla/show_bug.cgi?id=57640

I think this feature would be very interesting to our users:

   - https://stackoverflow.com/questions/10312281/change-the-
   thread-count-of-test-plan-in-jmeter-at-run-time
   
<https://stackoverflow.com/questions/10312281/change-the-thread-count-of-test-plan-in-jmeter-at-run-time>
   - https://stackoverflow.com/questions/47471907/increase-
   number-of-threads-in-jmeter-during-execution
   
<https://stackoverflow.com/questions/47471907/increase-number-of-threads-in-jmeter-during-execution>

I wouldn't say that we have currently an optimal way to do that if any, so
could we start thinking about it ?.

What do you think about those first ideas:
*Interface:*

   - Using the same approach as stopTest and shutdownTest :
      - We would need to define a request format for command 'MODIFY_LOAD':
         - addThreads=threadGroupName=<Positive or negative
         value>|threadGroupName2=<Positive or negative value>|
         - addDuration=threadGroupName=<Positive or negative
         value>|threadGroupName2=<Positive or negative value>|
         - pause
         - resume
         - Or embed an HTTP server which would also be nice for other
   reasons and would make it more usable for newbies

*Engine implementation:*

Now for  the implementation of operations:

   - addThreads is already available but only for positive values
   - duration : needs further thinking
   - pause : we could test for pause in JMeterThread main loop, if
   triggered we would wait on an object. It could be more complex if during
   rampup. It could be a limitation to start with
   - resume : we would notify waiters.

We could work on both items independently , provide a UDP based solution to
start with and then an HTTP server based one.
-- 
Regards.
Philippe M.

Reply via email to