[Bug 63150] The Throughput can Be also able to control At Transaction level, not only at Request/Hits Level.

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=63150

Ram <ra...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 OS|                            |All
            Summary|I want to Control the       |The Throughput can Be also
                   |Throughput at Transaction   |able to control At
                   |level, But not at           |Transaction level, not only
                   |Request/Hits Level.         |at Request/Hits Level.

--- Comment #1 from Ram <ra...@gmail.com> ---
For Ex: 
I am executing the tests with Apache JMeter and also using BlazeMeter. I have
one requirement, I have multiple transactions in one scenario, and each
transaction contains multiple requests, I want to achieve TPS per transaction
level. 
Then in this case, Throughput shaping timer, Constant throughput timer, Precise
Throughput Timer and Limit RPS(BlazeMeter) are not working. Even I tried with
yaml configuration also, but that also didnt worked. 
Could you please tell me how can I achieve it through yaml if possible.

EX: 
If number of Tx's in scenario = 3 
TPS targeted per Tx = 20 
I need to achieve each transaction controller to achieve 20 TPS and 
Total scenario TPS will be= 60.

Please suggest me how can I do this and do Enhance this feature if possible.

Taurus Configuration in YAML I did is:

modules: jmeter: 
properties: httpsampler.ignore_failed_embedded_resources: true 
execution: 
- concurrency: 50 
hold-for: 5m 
ramp-up: 1m 
throughput:60 
steps: 3 
scenario: Thread Group

scenarios: Thread Group: retrieve-resources: false script: Blazedemo.jmx

-- 
You are receiving this mail because:
You are the assignee for the bug.