The Constant Throughput Timer and the ones from the plugin allow JMeter as
well to compensate for loss of throughput due to poor response times.
However if you have to continue testing with the same virtual user (same
authentication credential), then limit the problematic request sampler so it
I wasn't familiar with the Throughput Shaping Timer, it seems like what we
need.
The only drawback of this solution is that we have some extra threads
waiting to be executed.
I will give it a try soon and probably will use it often.
On Tue, Sep 13, 2011 at 9:44 PM, Deepak Shetty
Hi,
What I'm doing is calculating it like this:
If I want a specific Sampler/iteration to be executed in a certain
frequency, for example 6000 Samples/iterations per Minute and supposed we
set 100 threads, put a timer on the thread group / sampler and calculate the
timer like this:
timer = 6000
Maybe you can use the Throughput Shaping Timer,
offered by the following link:
http://code.google.com/p/jmeter-plugins/
Kind Regards / Met vriendelijke groet,
Chris Meinster / Capgemini Outsourcing
Tester N29 TestOS
[cid:image001.jpg@01CC7206.5DBE13D0]
Com1: +31 6 46706779
Building Atlas Arena
You shouldnt use Constant timer for such requirements , because that would
need you to know in advance the average time your request responds in - for
you to be able to calculate the delay you need to get the rate of requests
you want
These type of requirements are met by the constant throughput
On 13 September 2011 09:59, Shmuel Krakower shmul...@gmail.com wrote:
Hi,
What I'm doing is calculating it like this:
If I want a specific Sampler/iteration to be executed in a certain
frequency, for example 6000 Samples/iterations per Minute and supposed we
set 100 threads, put a timer on
Hi,
I am using JMeter(2.4) for doing the loading testing of XMPP server and my test
plan is configured as following:
- Test plan
- Thread group
- Loop Controller
- Java Request
- Generate Summary Results
- Constant timer/Constant throughput timer
- CSV Data Set
7 matches
Mail list logo
