Yes, threads=users. 100 Users=100 Threads. Jmeter user pages http://jmeter.apache.org/usermanual/test_plan.html suggest
"Start with Ramp-up = number of threads and adjust up or down as needed." I am not really sure on what basis to adjust up or down, so I just leave ramp equal to number of threads (aka users). But does anyone know why, on average, per thread speed is faster when there are more threads/users. 1 thread = 1.402s 10 threads =1.707s 50 threads =1.087s 100 threads =0.813s I thought the more threads, the busier the servers and the slower the speed. -------------------------------------------- On Fri, 9/19/14, Deepak Shetty <[email protected]> wrote: Subject: Re: Faster speed with higher threads To: "JMeter Users List" <[email protected]> Date: Friday, September 19, 2014, 4:43 PM Im assuming that for you 1 thread = 1 user - so when you say 100 users u actually mean 100 threads? >Ramp is equal to the number of threads. so you have set ramp up to 100 seconds for 100 users? You aren't generating much concurrent load if one test is usually done in 1 -2 seconds. On Fri, Sep 19, 2014 at 12:59 PM, rxfillpharm <[email protected] > wrote: > Hi, > My test signs on and signsoff a web site. Ramp is equal to the number of > threads. > Here are the results: > > (First we recycle all servers) > 1 user= 1.402s > 10 users=1.707s > 50 user=1.087s > 100 users=0.813s > > Why are 100 users faster on average, than fewer users? > > My education in jmeter is expanding but I still have the nagging questions > . > Thank you. > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
