Forum Discussion

BenX's avatar
BenX
Contributor
16 years ago

Thread Startup Delay

Hi!

I think Thread Startup Delay is not working in load test when Fixed Rate strategy is choosen.
It looks like threads are starting with delay but nothing is happening. Then, suddenly, when the last thread should be started, all threads start at once. (and kill our server!    ...and my nerves  )


Build 3.0-pro-daily-build-2009-11-19-[1], Build Date 2009/11/19 05:19

With best regards,
Beno

5 Replies

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    16 years ago
    Hello,

    The FixedRate Strategy manages threads itself to be able to sustain a fixed rate of requests, and thus the Thread Startup Delay option isn't applicable for this strategy. However, it isn't right that setting the option to a nonzero value should cause problems for the delay, so I'll see if I can fix that. The correct behavior for this strategy is to simply ignore the Thread Startup Delay, hopefully tomorrows nightly build will have a fix for this.

    Regards,
    Dain
    eviware.com
  • BenX's avatar
    BenX
    Contributor
    16 years ago
    I see.
    Here's my situation...
    I have to run load test with 50 TPS. That's achieved with 3 or 4 threads. No problem at all.
    Now i would like to run 50TPS, but with 300 threads! SoapUI will never go after 300 because, as i said, 3 or 4 threads are enough to generate 50TPS.

    I'm glad if you can do something about this.
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    16 years ago
    Hello,

    This really can't be done using this strategy, and there shouldn't be a reason to do so either. The server has no concept of the number of threads running in soapUI, only the amount of transactions it has to handle. The FixedRate Strategy lets you set the desired TPS, and soapUI will create new threads to keep up with that demand. If more Threads were started then they would just sit there waiting, doing nothing at all.

    If you really want soapUI to run 300 threads, you could use the Simple Thread Strategy and manually set 300 Threads. This would give you a MUCH higher TPS than 50 though, so you would also have to add a delay step in your TestCase. Doing this no longer guarantees 50 TPS. By changing the delay time, you can get close to 50 TPS (the exact delay time required depends on the time the actual requests take, and can even vary for each run). What exactly is your reason for wanting 300 Threads?

    Regards,
    Dain
    eviware.com
  • Beno_Iskratel's avatar
    Beno_Iskratel
    Frequent Contributor
    16 years ago
    one more thing...

    when using Fixed-Rate strategy, SoapUI starts new threads very quickly.
    i set 200 for Max Threads.
    It would be nice if SoapUI would use Thread Startup Delay in this load test strategy as well.
    now threads are started to quickly and our servers can't handle situations like this.

    can there be done something about this?

    with best regards,
    beno