You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by David Patrick <da...@mac.com> on 2011/03/24 17:48:01 UTC
best place to put a constant throughput
Hi collective - quick question for you all.
given the outline description of the test below, where is the best place to put a constant throughput timer to achieve a rate of 12 orders per minute (effectively 12 iterations of 'Loop Controller' per minute)
+ Thread Group
+ HTTP Request Defaults
+ HTTP Cookie Manager
+ HTTP Header Manager
+ CSV Data Set Config
+ Loop Controller
+ Login
+ Place next order from CSV Input File
+ Logout
+ Success Results Tree
+ Error Results Tree
+ All Results Tree
+ Aggregate Report
Loop Controller is defined by the number of rows in the CSV file defined in the CSV Data Set Config item.
Cheers,
David
Sent from my iPhone
Re: RE: best place to put a constant throughput
Posted by "david.m1fcf" <da...@mac.com>.
many thanks - worked exactly as described!
On 25 Mar, 2011,at 07:47 AM, Ragini Thakur <ra...@cybage.com> wrote:
> Sorry My bad.
>
> You have 3 samplers under Loop controller. So if you only want to
> control throughput of Place order add the timer as child.
>
> Note that the timer will be applied before the sampler is executed.
>
> Regards,
> Ragini Thakur, System Analyst
> Phone(O):+91-20-66041700 Ext. 6479
>
>
> -----Original Message-----
> From: Ragini Thakur [mailto:raginit@cybage.com]
> Sent: Friday, March 25, 2011 1:02 PM
> To: JMeter Users List
> Subject: RE: best place to put a constant throughput
>
> The timers are processed before each sampler in the scope in which they
> are found; looking at your test plan you can either put it under Thread
> group or Loop controller, as you have only one sampler under your thread
> group.
>
> But if you are going to add more samplers to thread group then put it
> under Loop controller.
>
> Regards,
> Ragini Thakur
>
> -----Original Message-----
> From: David Patrick [mailto:david.m1fcf@mac.com]
> Sent: Friday, March 25, 2011 11:56 AM
> To: JMeter Users List
> Subject: Re: best place to put a constant throughput
>
> Hi guys - another quick push of this question if I may.
>
> The target performance for our system is somewhere around 50 order
> journeys per minute with a load of 400 users, so am using 4 instances of
> JMeter (100 users each at 12 orders per minute) to simulate this.
>
> What I am being asked to show within the script is that the system is
> capable of handling the steps inside the Loop Controller at a rate of 12
> orders per minute.
>
> The documentation I can find for the Constant Throughput Controller
> doesnt really give away the best place to put it to get what I need - so
> am coming to the larger User Community for some ideas.
>
> Cheers,
> David
>
> --
> David Patrick
> david.m1fcf@mac.com
>
> On 24 Mar 2011, at 16:48, David Patrick wrote:
>
> > Hi collective - quick question for you all.
> >
> > given the outline description of the test below, where is the best
> place to put a constant throughput timer to achieve a rate of 12 orders
> per minute (effectively 12 iterations of 'Loop Controller' per minute)
> >
> > + Thread Group
> > + HTTP Request Defaults
> > + HTTP Cookie Manager
> > + HTTP Header Manager
> > + CSV Data Set Config
> > + Loop Controller
> > + Login
> > + Place next order from CSV Input File
> > + Logout
> > + Success Results Tree
> > + Error Results Tree
> > + All Results Tree
> > + Aggregate Report
> >
> > Loop Controller is defined by the number of rows in the CSV file
> defined in the CSV Data Set Config item.
> >
> > Cheers,
> > David
> >
> > Sent from my iPhone
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
>
> "Legal Disclaimer: This electronic message and all contents contain
> information from Cybage Software Private Limited which may be
> privileged, confidential, or otherwise protected from disclosure. The
> information is intended to be for the addressee(s) only. If you are not
> an addressee, any disclosure, copy, distribution, or use of the contents
> of this message is strictly prohibited. If you have received this
> electronic message in error please notify the sender by reply e-mail to
> and destroy the original message and all copies. Cybage has taken every
> reasonable precaution to minimize the risk of malicious content in the
> mail, but is not liable for any damage you may sustain as a result of
> any malicious content in this e-mail. You should carry out your own
> malicious content checks before opening the e-mail or attachment."
> www.cybage.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
>
> "Legal Disclaimer: This electronic message and all contents contain information from Cybage Software Private Limited which may be privileged, confidential, or otherwise protected from disclosure. The information is intended to be for the addressee(s) only. If you are not an addressee, any disclosure, copy, distribution, or use of the contents of this message is strictly prohibited. If you have received this electronic message in error please notify the sender by reply e-mail to and destroy the original message and all copies. Cybage has taken every reasonable precaution to minimize the risk of malicious content in the mail, but is not liable for any damage you may sustain as a result of any malicious content in this e-mail. You should carry out your own malicious content checks before opening the e-mail or attachment."
> www.cybage.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
RE: best place to put a constant throughput
Posted by Ragini Thakur <ra...@cybage.com>.
Sorry My bad.
You have 3 samplers under Loop controller. So if you only want to
control throughput of Place order add the timer as child.
Note that the timer will be applied before the sampler is executed.
Regards,
Ragini Thakur, System Analyst
Phone(O):+91-20-66041700 Ext. 6479
-----Original Message-----
From: Ragini Thakur [mailto:raginit@cybage.com]
Sent: Friday, March 25, 2011 1:02 PM
To: JMeter Users List
Subject: RE: best place to put a constant throughput
The timers are processed before each sampler in the scope in which they
are found; looking at your test plan you can either put it under Thread
group or Loop controller, as you have only one sampler under your thread
group.
But if you are going to add more samplers to thread group then put it
under Loop controller.
Regards,
Ragini Thakur
-----Original Message-----
From: David Patrick [mailto:david.m1fcf@mac.com]
Sent: Friday, March 25, 2011 11:56 AM
To: JMeter Users List
Subject: Re: best place to put a constant throughput
Hi guys - another quick push of this question if I may.
The target performance for our system is somewhere around 50 order
journeys per minute with a load of 400 users, so am using 4 instances of
JMeter (100 users each at 12 orders per minute) to simulate this.
What I am being asked to show within the script is that the system is
capable of handling the steps inside the Loop Controller at a rate of 12
orders per minute.
The documentation I can find for the Constant Throughput Controller
doesnt really give away the best place to put it to get what I need - so
am coming to the larger User Community for some ideas.
Cheers,
David
--
David Patrick
david.m1fcf@mac.com
On 24 Mar 2011, at 16:48, David Patrick wrote:
> Hi collective - quick question for you all.
>
> given the outline description of the test below, where is the best
place to put a constant throughput timer to achieve a rate of 12 orders
per minute (effectively 12 iterations of 'Loop Controller' per minute)
>
> + Thread Group
> + HTTP Request Defaults
> + HTTP Cookie Manager
> + HTTP Header Manager
> + CSV Data Set Config
> + Loop Controller
> + Login
> + Place next order from CSV Input File
> + Logout
> + Success Results Tree
> + Error Results Tree
> + All Results Tree
> + Aggregate Report
>
> Loop Controller is defined by the number of rows in the CSV file
defined in the CSV Data Set Config item.
>
> Cheers,
> David
>
> Sent from my iPhone
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
"Legal Disclaimer: This electronic message and all contents contain
information from Cybage Software Private Limited which may be
privileged, confidential, or otherwise protected from disclosure. The
information is intended to be for the addressee(s) only. If you are not
an addressee, any disclosure, copy, distribution, or use of the contents
of this message is strictly prohibited. If you have received this
electronic message in error please notify the sender by reply e-mail to
and destroy the original message and all copies. Cybage has taken every
reasonable precaution to minimize the risk of malicious content in the
mail, but is not liable for any damage you may sustain as a result of
any malicious content in this e-mail. You should carry out your own
malicious content checks before opening the e-mail or attachment."
www.cybage.com
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
"Legal Disclaimer: This electronic message and all contents contain information from Cybage Software Private Limited which may be privileged, confidential, or otherwise protected from disclosure. The information is intended to be for the addressee(s) only. If you are not an addressee, any disclosure, copy, distribution, or use of the contents of this message is strictly prohibited. If you have received this electronic message in error please notify the sender by reply e-mail to and destroy the original message and all copies. Cybage has taken every reasonable precaution to minimize the risk of malicious content in the mail, but is not liable for any damage you may sustain as a result of any malicious content in this e-mail. You should carry out your own malicious content checks before opening the e-mail or attachment."
www.cybage.com
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
RE: best place to put a constant throughput
Posted by Ragini Thakur <ra...@cybage.com>.
The timers are processed before each sampler in the scope in which they
are found; looking at your test plan you can either put it under Thread
group or Loop controller, as you have only one sampler under your thread
group.
But if you are going to add more samplers to thread group then put it
under Loop controller.
Regards,
Ragini Thakur
-----Original Message-----
From: David Patrick [mailto:david.m1fcf@mac.com]
Sent: Friday, March 25, 2011 11:56 AM
To: JMeter Users List
Subject: Re: best place to put a constant throughput
Hi guys - another quick push of this question if I may.
The target performance for our system is somewhere around 50 order
journeys per minute with a load of 400 users, so am using 4 instances of
JMeter (100 users each at 12 orders per minute) to simulate this.
What I am being asked to show within the script is that the system is
capable of handling the steps inside the Loop Controller at a rate of 12
orders per minute.
The documentation I can find for the Constant Throughput Controller
doesnt really give away the best place to put it to get what I need - so
am coming to the larger User Community for some ideas.
Cheers,
David
--
David Patrick
david.m1fcf@mac.com
On 24 Mar 2011, at 16:48, David Patrick wrote:
> Hi collective - quick question for you all.
>
> given the outline description of the test below, where is the best
place to put a constant throughput timer to achieve a rate of 12 orders
per minute (effectively 12 iterations of 'Loop Controller' per minute)
>
> + Thread Group
> + HTTP Request Defaults
> + HTTP Cookie Manager
> + HTTP Header Manager
> + CSV Data Set Config
> + Loop Controller
> + Login
> + Place next order from CSV Input File
> + Logout
> + Success Results Tree
> + Error Results Tree
> + All Results Tree
> + Aggregate Report
>
> Loop Controller is defined by the number of rows in the CSV file
defined in the CSV Data Set Config item.
>
> Cheers,
> David
>
> Sent from my iPhone
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
"Legal Disclaimer: This electronic message and all contents contain information from Cybage Software Private Limited which may be privileged, confidential, or otherwise protected from disclosure. The information is intended to be for the addressee(s) only. If you are not an addressee, any disclosure, copy, distribution, or use of the contents of this message is strictly prohibited. If you have received this electronic message in error please notify the sender by reply e-mail to and destroy the original message and all copies. Cybage has taken every reasonable precaution to minimize the risk of malicious content in the mail, but is not liable for any damage you may sustain as a result of any malicious content in this e-mail. You should carry out your own malicious content checks before opening the e-mail or attachment."
www.cybage.com
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: best place to put a constant throughput
Posted by David Patrick <da...@mac.com>.
Hi guys - another quick push of this question if I may.
The target performance for our system is somewhere around 50 order journeys per minute with a load of 400 users, so am using 4 instances of JMeter (100 users each at 12 orders per minute) to simulate this.
What I am being asked to show within the script is that the system is capable of handling the steps inside the Loop Controller at a rate of 12 orders per minute.
The documentation I can find for the Constant Throughput Controller doesnt really give away the best place to put it to get what I need - so am coming to the larger User Community for some ideas.
Cheers,
David
--
David Patrick
david.m1fcf@mac.com
On 24 Mar 2011, at 16:48, David Patrick wrote:
> Hi collective - quick question for you all.
>
> given the outline description of the test below, where is the best place to put a constant throughput timer to achieve a rate of 12 orders per minute (effectively 12 iterations of 'Loop Controller' per minute)
>
> + Thread Group
> + HTTP Request Defaults
> + HTTP Cookie Manager
> + HTTP Header Manager
> + CSV Data Set Config
> + Loop Controller
> + Login
> + Place next order from CSV Input File
> + Logout
> + Success Results Tree
> + Error Results Tree
> + All Results Tree
> + Aggregate Report
>
> Loop Controller is defined by the number of rows in the CSV file defined in the CSV Data Set Config item.
>
> Cheers,
> David
>
> Sent from my iPhone
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org