New answers tagged

1

If you have 100 Threads in thread group and Ramp up time as 20, these 100 threads aren't concurrent. To maintain concurrency for 100 threads you have to use either loop counts or Durations (Scheduler in Thread Group). You may try with the "Ultimate Thread Group" (JMeter plugins) instead of only "Thread group". To check this, you can use "Active Threads Over ...


2

It depends. JMeter acts as follows: JMeter starts defined number of threads during ramp-up period Threads start executing samplers upside down (or according to Logic Controllers) When thread doesn't have any more samplers to execute or loops to iterate - it's being shut down So if your test is short enough you may easily run into a situation when 1st ...


1

set ramp up time to zero to start all the thread at same time. difference in starting time between threads = Ramp up time/ no of threads. If you have ramp up time = 20 and no of threads = 100 then each thread with start with time gap of 0.2 (20/100) sec from previous thread


0

As per your configuration, each thread(user) will start their action after 20/100 =0.2 seconds. i.e. after first thread has initiated, second thread will start after 0.2 seconds. If you want to verify the same from Jmeter, on the top right corner threads are shown once you start the action.


0

This might be because some of application requests are taking too long to execute, holding the application server’s threads busy, and not allowing the resources to be used by incoming requests. Try the running the test with 4000 concurrent users, then 6000 users and so on. Check at number of request you are getting this error.You must verify Apache ...


2

This is a network constraint over which you may not have any control. Do you know after what time you get this error? You could play with Timeouts section on HTTP Request Sample and keep it higher than the time which causes timeout error.



Top 50 recent answers are included