You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jmeter.apache.org by bu...@apache.org on 2019/02/07 07:51:25 UTC
[Bug 63150] New: I want to Control the Throughput at Transaction
level, But not at Request/Hits Level.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63150
Bug ID: 63150
Summary: I want to Control the Throughput at Transaction level,
But not at Request/Hits Level.
Product: JMeter
Version: unspecified
Hardware: PC
Status: NEW
Severity: enhancement
Priority: P2
Component: Main
Assignee: issues@jmeter.apache.org
Reporter: ramu814.d@gmail.com
Target Milestone: JMETER_5.1
Hi Team,
Hope you are doing well.
I want to Control the Throughput at Transaction level, But not at Request/Hits
Level.
Means for Ex:
I have 3 Transactions In a scenario, with 3 requsts in Transaction-1, 6 requsts
in Transaction-1 and 4 requsts in Transaction-1.
Here I want to achieve the Uniform Throughput for all the Transactions
Irrespective of number of Requests in the each Transaction.
I tried with Constant Throughput Timer, Precise Throughput Timer and Throughput
Shaping Timer, but As they are designed to control at Samples/Request level,
not at Transaction level, I am not able to achieve The Targetted throughput.
Could you plese hep me In this, How can I control the Throughput at Transaction
level.
If I can update the JMeter Throughput Shaping Timer code to work at Transaction
level, pls guide me in that point alos, how can I do it.
Thanks.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 63150] The Throughput can Be also able to control At
Transaction level, not only at Request/Hits Level.
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63150
Vladimir Sitnikov <si...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #7 from Vladimir Sitnikov <si...@gmail.com> ---
Closing as it is not a bug in JMeter.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 63150] The Throughput can Be also able to control At
Transaction level, not only at Request/Hits Level.
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63150
--- Comment #4 from Vladimir Sitnikov <si...@gmail.com> ---
@Ram,
I can't open your file (error is below).
Can you please use just default JMeter samplers and listeners?
Problem loading XML from:'/Users/vladimirsitnikov/Documents/NEWTOURS (1).jmx'.
Cause:
CannotResolveClassException: kg.apc.jmeter.vizualizers.CorrectedResultCollector
Detail:com.thoughtworks.xstream.converters.ConversionException:
---- Debugging information ----
cause-exception : com.thoughtworks.xstream.converters.ConversionException
cause-message :
first-jmeter-class :
org.apache.jmeter.save.converters.HashTreeConverter.unmarshal(HashTreeConverter.java:67)
class : org.apache.jmeter.save.ScriptWrapper
required-type : org.apache.jmeter.save.ScriptWrapper
converter-type : org.apache.jmeter.save.ScriptWrapperConverter
path :
/jmeterTestPlan/hashTree/hashTree/kg.apc.jmeter.vizualizers.CorrectedResultCollector
line number : 88
version : 5.1-SNAPSHOT.20190207
-------------------------------
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 63150] The Throughput can Be also able to control At
Transaction level, not only at Request/Hits Level.
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63150
--- Comment #5 from Ram <ra...@gmail.com> ---
Created attachment 36431
--> https://bz.apache.org/bugzilla/attachment.cgi?id=36431&action=edit
Sample JMeter Test Plan
Hi Vladimir,
Sorry for the inconvenience.
Please find the attached TestPlan.
Thanks,
Ram
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 63150] The Throughput can Be also able to control At
Transaction level, not only at Request/Hits Level.
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63150
--- Comment #6 from Vladimir Sitnikov <si...@gmail.com> ---
Thanks.
The thing is you place "Constant Throughput Timer" at the top of the tree, so
the timer is effectively inherited by all the sibling transaction controllers
and their children samplers. This is what results in "at hits level".
You need to wrap "Constant Throughput Timer" with a "Flow Control Action". That
would avoid inheritance of the timer to all the other samplers.
Vladimir
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 63150] The Throughput can Be also able to control At
Transaction level, not only at Request/Hits Level.
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63150
Ram <ra...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ramu814.d@gmail.com
--- Comment #3 from Ram <ra...@gmail.com> ---
Created attachment 36430
--> https://bz.apache.org/bugzilla/attachment.cgi?id=36430&action=edit
Sample JMeter Test Plan
Hi Vladimir,
Hope you are doing well, Thanks for the Response.
Here I attached the sample test plan, and In this for ex: As I mentioned below,
Irrespective of number of requests per Transaction, I want to achieve the
Targeted Throughput for all the Transactions in the scenario.
Could you please help me here.
As per my understanding the Throughput Shaping Timer/Constant Throughput
Timer/Precise Throughput Timer are all working at Request level, and As all the
transactions will not have equal number of requests, I am getting inequal
throughput for Transaction to Transaction, which is totally deviating the Test
Requirement.
In parallel to this, I am also checking with JMeter Plugin Source code, if we
can override the functionality to check the Throughput for Transaction Level to
control it, inspite of doing control by Request level.
Thanks,
Ram
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 63150] The Throughput can Be also able to control At
Transaction level, not only at Request/Hits Level.
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63150
--- Comment #8 from Ram <ra...@gmail.com> ---
Thanks Vladimir,
I will follow in the same way.
Regards,
ram
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 63150] The Throughput can Be also able to control At
Transaction level, not only at Request/Hits Level.
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63150
Philippe Mouawad <p....@ubik-ingenierie.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|JMETER_5.1 |---
Resolution|INVALID |WORKSFORME
CC| |p.mouawad@ubik-ingenierie.c
| |om
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 63150] The Throughput can Be also able to control At
Transaction level, not only at Request/Hits Level.
Posted by 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.
[Bug 63150] The Throughput can Be also able to control At
Transaction level, not only at Request/Hits Level.
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63150
--- Comment #2 from Vladimir Sitnikov <si...@gmail.com> ---
@Ram, please share a simple test plan.
--
You are receiving this mail because:
You are the assignee for the bug.