jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcelo Jara <marceloj...@hotmail.com>
Subject Constant Throughput Timer limitation or bug?
Date Wed, 18 Feb 2015 19:36:49 GMT
I am using Jmeter 2.12 and noticed that during a test, the transactions per second was much
higher than I had configured. Using a value of 15000 (250 TPS) works as expected. If I go
to 15001, the TPS jumps to 333. Here are some more results:
CTP = 15000, expected = 250 tps, result 250 tpsCTP = 15001, expected = 250 tps, result 333
tps
CTP = 20000, expected = 333 tps, result 333 tpsCTP = 20001, expected = 333 tps, result 500
tps
CTP = 30000, expected = 500 tps, result 500 tpsCTP = 30001, expected = 500 tps, result 1000
tps


I was able to create a simple test plan that exhibits the same issue. 
Thread Group (100 threads, loop forever,scheduler with duration of 60)---- Debug Sampler (all
defaults)      ---- CTP (all active threads in current thread group (shared)


Anyone else run into this? 
Thanks,
Marcelo 		 	   		  
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message