g the
>> neighbours ;-).
>>
>> >> On Thu, Oct 20, 2011 at 10:43 AM, sebb wrote:
>> >>
>> >>> On 20 October 2011 18:14, Adrian Speteanu wrote:
>> >>> > Hey David,
>> >>> >
>> >>> > I've us
b wrote:
> >>
> >>> On 20 October 2011 18:14, Adrian Speteanu wrote:
> >>> > Hey David,
> >>> >
> >>> > I've used both.
> >>> >
> >>> > Its not much to compare :). If you understand the Constant Th
2011 at 10:43 AM, sebb wrote:
>>
>>> On 20 October 2011 18:14, Adrian Speteanu wrote:
>>> > Hey David,
>>> >
>>> > I've used both.
>>> >
>>> > Its not much to compare :). If you understand the Constant Throughput
>&
increment to define the throughput variable.
> On Thu, Oct 20, 2011 at 10:43 AM, sebb wrote:
>
>> On 20 October 2011 18:14, Adrian Speteanu wrote:
>> > Hey David,
>> >
>> > I've used both.
>> >
>> > Its not much to compare :). If you
Thanks, the beanshell server looks useful for what I'd want.
On Thu, Oct 20, 2011 at 10:43 AM, sebb wrote:
> On 20 October 2011 18:14, Adrian Speteanu wrote:
> > Hey David,
> >
> > I've used both.
> >
> > Its not much to compare :). If you understan
On 20 October 2011 18:14, Adrian Speteanu wrote:
> Hey David,
>
> I've used both.
>
> Its not much to compare :). If you understand the Constant Throughput Timer,
> then you understand both and it's easy to see that its major limitation is
> that it holds (if possi
Hey David,
I've used both.
Its not much to compare :). If you understand the Constant Throughput Timer,
then you understand both and it's easy to see that its major limitation is
that it holds (if possible) the throughput constant at the value you define
(which was the intent). Howe
There is example test plan shipped with plugins. Try looking at it, it
illustrates the capabilities of Throughput Shaping Timer.
-
--
Andrey Pohilko
JP@GC Maintainer
--
View this message in context:
http://jmeter.512774.n5.nabble.com/Constant-Throughput-Timer-vs-Throughput-Shaping-Timer
I was wondering if anybody has used both, and wonder how they compare.
Pros/cons of each.
And how one could best simulate the Throughput Shaping Timer with the
constant throughput timer via variable/property that defines the throughput
and changing it during test run. Particularly how would you
g, the OS may have had time to free up the resources
>>> or
>>> >> not.
>>> >> >
>>> >> >> On Wed, Sep 14, 2011 at 3:45 AM, sebb wrote:
>>> >> >>>
>>> >> >>> On
ces
>> or
>> >> not.
>> >> >
>> >> >> On Wed, Sep 14, 2011 at 3:45 AM, sebb wrote:
>> >> >>>
>> >> >>> On 14 September 2011 04:51, E S
>> wrote:
>> >> >>> > To answer your qu
e:
> >> >>>
> >> >>> On 14 September 2011 04:51, E S
> wrote:
> >> >>> > To answer your question, on the 6000 req/sec tests where this is
> no
> >> >>> > throughput timer, it's about what you would expect, arou
ould expect, around 30 ms for
>> the
>> >>> > average request. So that means each thread can do about 33 request
>> per
>> >>> > second and if you have 200 threads that's roughly 6000 requests per
>> second.
>> >>> >
>> >
t;>> > throughput timer, it's about what you would expect, around 30 ms for
> the
> >>> > average request. So that means each thread can do about 33 request
> per
> >>> > second and if you have 200 threads that's roughly 6000 request
box is near the limit of ports, then changes in timing might
>>> have an effect.
>>>
>>> Which HTTP sampler are you using?
>>> HttpClient4 (in version 2.5; fixed but not yet released) has an
>>> unfortunate bug that means it uses up lots of c
hreads that's roughly 6000 requests per second.
>> >
>> > I did just notice something significant though. I am getting errors on the
>> > tests that use the constant throughput timer. Some of the requests (usually
>> > around 10%) give the following error:
>&g
000 requests per second.
> >
> > I did just notice something significant though. I am getting errors on the
> > tests that use the constant throughput timer. Some of the requests (usually
> > around 10%) give the following error:
> >
> > "Response code: Non
have 200 threads that's roughly 6000 requests per second.
>
> I did just notice something significant though. I am getting errors on the
> tests that use the constant throughput timer. Some of the requests (usually
> around 10%) give the following error:
>
>
nd.
I did just notice something significant though. I am getting errors on the
tests that use the constant throughput timer. Some of the requests (usually
around 10%) give the following error:
"Response code: Non HTTP response code: java.net.NoRouteToHostException
Response message: Non HTTP r
What are the response times when you run these tests?
-
http://www.http503.com/
--
View this message in context:
http://jmeter.512774.n5.nabble.com/Constant-throughput-timer-not-giving-expected-results-tp4784904p4797538.html
Sent from the JMeter - User mailing list archive at Nabble.com
Well I did some more testing and I have to say that I'm still confused. All
I can figure is that I am misunderstanding how the constant throughput timer
works.
I was able to configure the throughput timer to get the same results as I
did without it (6000 req/sec) but I had to set the
On 9 September 2011 04:31, E S wrote:
> I'm having some trouble getting the Constant Throughput Timer to work the
> way I want in certain cases.
>
> I have a single thread group of 100 threads, all of which are requesting the
> same resource over and over for 1 minute.
>
time your
request takes to respond - either way, if you want more throughput you'll
probably need more threads.
-
http://www.http503.com/
--
View this message in context:
http://jmeter.512774.n5.nabble.com/Constant-throughput-timer-not-giving-expected-results-tp4784904p4785825.html
Sent
.512774.n5.nabble.com/Constant-throughput-timer-not-giving-expected-results-tp4784904p4785802.html
Sent from the JMeter - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org
For
I'm having some trouble getting the Constant Throughput Timer to work the
way I want in certain cases.
I have a single thread group of 100 threads, all of which are requesting the
same resource over and over for 1 minute.
I attached a Constant Throughput Timer on the thread group and
Hi Oliver,
The transaction controller has a little checkbox: include timer duration in
> sample time (or something like that). So...
>
>
Uhhh yes indeed That helps, I am learning...
Thanks,
Andrej
The transaction controller has a little checkbox: include timer duration in
sample time (or something like that). So...
--
View this message in context:
http://jmeter.512774.n5.nabble.com/Constant-Throughput-Timer-and-elapsed-sample-time-tp4513032p4531284.html
Sent from the JMeter - User mailing
2, 2011 at 8:54 AM, Andrej van der Zee <
andrejvander...@gmail.com> wrote:
> Hi,
>
> I have a question about the Constant Throughput Timer. I have the
> following configuration:
>
> Thread Group (10 threads)
> ---> Transaction Controller
> ---> HTTP Reques
Hi,
I have a question about the Constant Throughput Timer. I have the
following configuration:
Thread Group (10 threads)
---> Transaction Controller
---> HTTP Request
---> View Results In Table
---> Constant Throughput Timer (60 samples per minute)
Now I noticed that the wait
Maybe http://code.google.com/p/jmeter-plugins/wiki/ThroughputShapingTimer
Throughput Shaping Timer can help you?
--
View this message in context:
http://jmeter.512774.n5.nabble.com/Constant-Throughput-timer-and-using-Calculate-throughput-based-on-all-active-threads-shared-tp4497627p4498497
idn't
really spend a long time playing around with it so perhaps I missed
something.
--
View this message in context:
http://jmeter.512774.n5.nabble.com/Constant-Throughput-timer-and-using-Calculate-throughput-based-on-all-active-threads-shared-tp4497627p4498476.html
Sent from the JMeter - User
We have a bunch of ThreadGroups each with a Constant Throughput Timer
using the mode "Calculate throughput based on all active threads
(shared)"
We are finding that if you start a large number of threads then they
all get to run once before the throughput will influence when to run
t
15, 2011 at 8:09 PM, zillakilla [via JMeter] <
ml-node+3386031-1849178308-146...@n5.nabble.com> wrote:
> I use this formulae:
> Constant throughput timer = number of threads * 60 (this equals 1 request
> per second per thread)
>
> Using this formulae I 'estimate
Thanks for the input,Again i tried the same as mentioned by you for 30
minutes but still the same thing is happening. I am not sure is the result
is coming wrong or correct. Please let me know Ideal Throughput should be as
per Constant throughput timer (samples/DurationToRun(Sec)) is expecting by
Thanks for the input,Again i tried the same as mentioned by you for 30
minutes but still the same thing is happening. I am not sure is the result
is coming wrong or correct. Please let me know Ideal Throughput should be as
per Constant throughput timer (samples/DurationToRun(Sec)) is expecting
Loops DurationToRun(Sec)
> ConstantThroughPutTimer(Samples/minute)
> Samples Throughput(Request/second) Ideal Throughput should be as per
> Constant throughput timer (samples/DurationToRun(Sec))
> 50 1 60 sec - 50 4.0/sec -
> 50 1 60 sec 240 50
cond) Ideal Throughput should be as per
Constant throughput timer (samples/DurationToRun(Sec))
50 1 60 sec - 50 4.0/sec -
50 1 60 sec 240 50 4.4/sec 4.0/sec
50 1 60 sec 120 50 4.0/sec 2.0/sec
100 1 60 sec -
>> With to scenarios 1st ) with average response time of 9 mseg 2nd ) with
> >> average of 100mseg
> >>
> >> The 1st case : Figure3.png, I am able to manage the 100reqxsec as is
> >> specified in the constant throughput timer, but 2nd case ) Figure4.png I
> >&
gure1.png and Figure2.png
>>
>> With to scenarios 1st ) with average response time of 9 mseg 2nd ) with
>> average of 100mseg
>>
>> The 1st case : Figure3.png, I am able to manage the 100reqxsec as is
>> specified in the constant throughput timer, but 2nd case ) F
the constant throughput timer, but 2nd case ) Figure4.png I
am only able to send 10 reqxsec. The only difference in the scenario is
the response time.
Do you find any explanation ?
You run with a single Thread, right?
Let's do the math:
Max throughput with 0.009sec/access:
(1 second) / (
Look Andrei,
I have following scenario : Figure1.png and Figure2.png
With to scenarios 1st ) with average response time of 9 mseg 2nd ) with
average of 100mseg
The 1st case : Figure3.png, I am able to manage the 100reqxsec as is
specified in the constant throughput timer, but 2nd case ) Figure4
Toni,
The Constant Throughput Timer will NOT affect the response time of
your requests.
It will, however, introduce a variable delay between samples, in order
to limit your Actions Per Minute to the specified value.
On Mon, Nov 8, 2010 at 10:21 PM, Toni Menendez Lopez
wrote:
> Hello everyb
Hello everybody,
Is there any way I can check relation between constant throughput timer and
response time in requests.
The thing is that in my application has a response time of 80mseg and
jmeter is not able to follow the throghput I set up in the constant
throughput timer !
Can anyone explain
late a number of phones (each of them connecting with a
> maximum
> download speed, let's say gprs) downloading files (whose size can vary).
>
> In similar cases I would compute an appropriate number of req/second and
> then input it in the Constant Throughput Timer but, as file si
gt; download speed, let's say gprs) downloading files (whose size can vary).
>
> In similar cases I would compute an appropriate number of req/second and
> then input it in the Constant Throughput Timer but, as file size can vary,
> it would be convenient to specify the throughput in
I need to simulate a number of phones (each of them connecting with a maximum
download speed, let's say gprs) downloading files (whose size can vary).
In similar cases I would compute an appropriate number of req/second and
then input it in the Constant Throughput Timer but, as file siz
On 03/04/2010, Patrick Li wrote:
> OK, I think I get it now. So, this should be independent of the number of
> concurrent threads too I guess since the timer should "control" all the
> active threads and put them on hold as needed in order to reach the desired
> throughput? i.e. 50 threads an
OK, I think I get it now. So, this should be independent of the number of
concurrent threads too I guess since the timer should "control" all the
active threads and put them on hold as needed in order to reach the desired
throughput? i.e. 50 threads and 100 threads should make little or no
differ
> > Date: Wed, 31 Mar 2010 11:29:08 +0100
> > Subject: Re: Constant Throughput Timer
> > From: seb...@gmail.com
> > To: jmeter-user@jakarta.apache.org
>
> >
> > On 31/03/2010, Patrick Li wrote:
> > >
> > > Hi,I am using Constant Throu
Hi,
Thanks, that makes sense. One more question, is it possible to achieve that
(continue sending requests regardless of server capacity) with some other
sort of timer or approach?
Thanks
Liang
> Date: Wed, 31 Mar 2010 11:29:08 +0100
> Subject: Re: Constant Throughput Timer
>
On 31/03/2010, Patrick Li wrote:
>
> Hi,I am using Constant Throughput Timer to control the number of requests
> made to the server per unit of time. The doc suggests that the actual
> throughput is dependent on the actual processing power. Is it possible to
> send request
Hi,I am using Constant Throughput Timer to control the number of requests made
to the server per unit of time. The doc suggests that the actual throughput is
dependent on the actual processing power. Is it possible to send requests
regardless if the server is capable of handling it? We are
.
-Original Message-
From: Pieter P [mailto:pie...@porthome.nl]
Sent: Wednesday, January 21, 2009 11:07 AM
To: jmeter-user@jakarta.apache.org
Subject: RE: Limit concurrent number of threads using Constant
Throughput Timer?
Hi Adrian,
I've configured the number of threads to 3000 such
ient?
>
> Regards,
>
> Adrian
>
> -Original Message-
> From: Pieter P [mailto:pie...@porthome.nl]
> Sent: 21 January 2009 15:39
> To: jmeter-user@jakarta.apache.org
> Subject: Limit concurrent number of threads using Constant Throughput
> Timer?
>
>
> **
r-user@jakarta.apache.org
> Subject: Limit concurrent number of threads using Constant Throughput
> Timer?
>
>
> *
>
> This e-mail has been received by the Revenue Internet e-mail service. (IP)
>
> ***
Subject: Limit concurrent number of threads using Constant Throughput
Timer?
*
This e-mail has been received by the Revenue Internet e-mail service. (IP)
*
Hello,
I'm using JMeter 2.3.2 to functionally test my web serve
read that the Constant Throughput Timer can be used to create
time-waits based on other variables than transaction-throughput, for example
based in the amount of currently running threads. I could not figure out how
to implement this, though..
Is it possible to limit the amount of concurrent
On 12/06/2008, Assaf49 <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I enjoy using Jmeter very much. I think it is a superb application.
> I am using Jmeter 2.3.1, but for some reason i can not add (via the Jmeter
> gui) more than one "Constant throughput timer"
Hi,
I enjoy using Jmeter very much. I think it is a superb application.
I am using Jmeter 2.3.1, but for some reason i can not add (via the Jmeter
gui) more than one "Constant throughput timer" to my test plan.
One "Constant throughput timer" works well. But the Jmeter GUI do
On 10/04/2008, joeweder <[EMAIL PROTECTED]> wrote:
>
> I would appreciate it if somebody can confirm that a "Constant Throughput
> Timer" will not INCREASE threads to meet throughput settings, it will only
> throttle down the threads specified in the test.
I would appreciate it if somebody can confirm that a "Constant Throughput
Timer" will not INCREASE threads to meet throughput settings, it will only
throttle down the threads specified in the test.
--
View this message in context:
http://www.nabble.com/Constant-Throughput-Time
I just have one constant throughput timer at the end of the test, i.e after
24 samples.
sebb-2-2 wrote:
>
> I think your problem might be due to the placement of the Timer.
>
> Timers are activated for every sampler which is in scope.
>
> Probably bes
gt;
> > On 14/11/2007, tiffany <[EMAIL PROTECTED]> wrote:
> >>
> >> I am using "all active threads in current thread group", what does this
> >> mean
> >> if I have the following configuration? Do I have to care number of
> >> threa
;, what does this
>> mean
>> if I have the following configuration? Do I have to care number of
>> threads
>> in this case to configure the constant throughput timer?
>>
>> threads: 10
>> Ramp up period: 60
>
> Every 6 seconds, another thread becomes
On 14/11/2007, tiffany <[EMAIL PROTECTED]> wrote:
>
> I am using "all active threads in current thread group", what does this mean
> if I have the following configuration? Do I have to care number of threads
> in this case to configure the constant throughput time
I am using "all active threads in current thread group", what does this mean
if I have the following configuration? Do I have to care number of threads
in this case to configure the constant throughput timer?
threads: 10
Ramp up period: 60
constant throughput timer: 17.0 ( I wa
On 09/11/2007, tiffany <[EMAIL PROTECTED]> wrote:
>
> The calculations is based on 1 thread (1 user) or number of threads doesn't
> count?
>
> Actually, I have a test with the following configuration:
>
> threads: 1
> iterations: 100
> constant throughput time
The calculations is based on 1 thread (1 user) or number of threads doesn't
count?
Actually, I have a test with the following configuration:
threads: 1
iterations: 100
constant throughput timer: 30.0 (all active threads in current thread group)
Frequency needs per hour: 200
By the calcu
> should I set in the Constant Throughput Timer ?)
>
> Thanks,
> Tiffany
> =
>
> sebb-2 wrote:
> >
> > Constant Timer always sleeps for the amount of time specified.
> >
> > Constant Throughput Timer sleeps for as long as necessary to t
Thanks for the answer.
I still have a question, if I want my test case which consists 9 requests
run 200 times per hour. How to calculate the throughput time for it(What
should I set in the Constant Throughput Timer ?)
Thanks,
Tiffany
=
sebb-2 wrote:
>
> Constant
Constant Timer always sleeps for the amount of time specified.
Constant Throughput Timer sleeps for as long as necessary to try and
maintain the throughput.
On 13/09/2007, tiffany <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I am not sure the difference % the usage of Constant
Hi,
I am not sure the difference % the usage of Constant Timer and Constant
throughput timer even I have read the user manual.
I try to do a web load test with 3 test cases, all 3 test cases are in a
test plan as the following:
- test plan
- thread group 1
- HTTP request
hread group. I let the requests run until completion and
> that takes 2 mins consistently.
>
> Now I add a 'Constant Throughput Timer' at the same scope as my samplers to
> throttle the throughput to 245 requests per minute. I expect the time taken
> to be just
Hi All,
I have a thread group for which I have 10 threads looping 10 times and I have 7
samplers in the thread group. I let the requests run until completion and that
takes 2 mins consistently.
Now I add a 'Constant Throughput Timer' at the same scope as my samplers to
th
Hi
What's the main difference between "calculate throughput based on"
parameter?
All actice threads, all active threads in current thread group
All actice threads (shared), all active threads in current thread group
(shared)
I have a thread group, which have 8 http requests, and each with a
"th
ays in the aggregate report give us that value?
(i.e if the I record the scripts for a simple "Add to shopping cart " use
case ..
--
View this message in context:
http://www.nabble.com/Constant-Throughput-Timer-tf2044856.html#a5632763
Sent from the JMeter - User forum at Nabble.com.
On 03/08/06, Srinims <[EMAIL PROTECTED]> wrote:
I was just quoting some values as examples. I don't think the functionality
of the Constant Throughput timer would change based on the ramp up time
.Pls let me know how the constant throughput timer is supposed to work .
It is do
I was just quoting some values as examples. I don't think the functionality
of the Constant Throughput timer would change based on the ramp up time
.Pls let me know how the constant throughput timer is supposed to work .
--
View this message in context:
http://www.nabble.com/Con
On 03/08/06, Srinims <[EMAIL PROTECTED]> wrote:
Hi Sebb/Peter ,
Please clarify the significance of using a constant throughput timer .
http://jakarta.apache.org/jmeter/usermanual/component_reference.html#Constant_Throughput_Timer
Now consider the following case:
No of threads : -10
Hi Sebb/Peter ,
Please clarify the significance of using a constant throughput timer .
Now consider the following case:
No of threads : -100
Ramp Up time -10 secs
In this case it would mean that the server would be hit 10 users /sec.
Now pls let me know how the usage of a constant throughput
July 28, 2006 5:30 PM
To: JMeter Users List
Subject: Re: Constant throughput timer question
Which version of JMeter are you using? There was an update to this in
version 2.2.
You may find you get better results if you do the calculation as "this
thread only".
On 28/07/06, James Bull &l
Thanks for that. I am on version 2.1.1 so I will give 2.2 a try.
Cheers
James
-sebb <[EMAIL PROTECTED]> wrote: -
To: "JMeter Users List"
From: sebb <[EMAIL PROTECTED]>
Date: 07/28/2006 01:00PM
Subject: Re: Constant throughput timer question
Which version of JMete
Which version of JMeter are you using? There was an update to this in
version 2.2.
You may find you get better results if you do the calculation as "this
thread only".
On 28/07/06, James Bull <[EMAIL PROTECTED]> wrote:
Hi all,
I have noticed while using the constant throughp
Hi all,
I have noticed while using the constant throughput timer that it calculates
its throughput only after the first set of threads has completed.
ie. if you set the throughput to 100 per minute but have 200 threads all
200 threads will run for an iteration and then wait for sufficient time
is that all the threads start at once,
> > > > > and having 100 thread groups with only 1 thread in each will make it
> > > > > tedious to fix - you'll need to add a gradually increasing delay to
> > > > > each of the thread groups.
> > > > >
> > I suspect part of the problem is that all the threads start at once,
> > > > and having 100 thread groups with only 1 thread in each will make it
> > > > tedious to fix - you'll need to add a gradually increasing delay to
> > > > each of the thread g
to add a gradually increasing delay to
> > > each of the thread groups.
> > > What happens if you have fewer thread groups and more threads in each
> > group?
> > > You can set the ramp-up for each thread-group to ensure that the
> > > threads start more evenl
hreads in each
> group?
> > You can set the ramp-up for each thread-group to ensure that the
> > threads start more evenly.
> >
> > S.
> > On 09/12/05, Iago Toral Quiroga <[EMAIL PROTECTED]> wrote:
> > > Hi,
> > >
> > > I've co
t; > Hi,
> > >
> > > I've configured a test with 100 thread groups (one thread per thread
> > > group) and added a constant throughput timer to get a 10 requests per
> > > second performance. To do so, I configured target throughput to 600
> > &g
On 09/12/05, Iago Toral Quiroga <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I've configured a test with 100 thread groups (one thread per thread
> > group) and added a constant throughput timer to get a 10 requests per
> > second performance. To do so, I con
ds in each group?
You can set the ramp-up for each thread-group to ensure that the
threads start more evenly.
S.
On 09/12/05, Iago Toral Quiroga <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I've configured a test with 100 thread groups (one thread per thread
> group) and added a cons
Hi,
I've configured a test with 100 thread groups (one thread per thread
group) and added a constant throughput timer to get a 10 requests per
second performance. To do so, I configured target throughput to 600
(samples per minute) and selected to compute performance based on all
active th
Hi,
I have been using JMeter2.1 .I need Constant
Throughput Timer to send limited load.But need to know
more about the operation of options under 'Calculate
Throughput based on'.
Thanks fo
Hi sebb,
In user manual Constant Throughput Timer
description is not related to 2.1 version. Please let
me know about the working of the options present.
--- sebb <[EMAIL PROTECTED]> wrote:
> Attachment did not make it to the list - but please
> don't send
> att
Attachment did not make it to the list - but please don't send
attachments to the list anyway.
Please raise a Bugzilla issue, and attach a test case to that.
S.
On 02/11/05, sarath chandra <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
>I have been using JMeter2.1 version.I need more
>
> information re
Hi All,
I have been using JMeter2.1 version.I need more
information regarding Constant Throughput Timer.I run
a test using 2 options of timer which can b found in
attachment.
I used 3 threads & in timer Target throughput(in
samples per minute) as 10.0,
first i used under time
Hi,
I have been using JMeter2.1 version.I need more
information regarding Constant Throughput Timer.I run
a test using 2 options of timer which can b found in
attachment.
I used 3 threads & in timer Target throughput(in
samples per minute) as 10.0,
first i used under timer Ca
/ 210 = 120 samples per
> minute. The problem is that the test completes in 2 hours and 20 minutes. I
> was under the impression that the constant throughput timer throttles the
> samples executed "within the container where you put the timer" which in my
> test is the thre
1285200 / 210 = 6120 samples
per minute and the second gets 25200 / 210 = 120 samples per minute. The
problem is that the test completes in 2 hours and 20 minutes. I was under the
impression that the constant throughput timer throttles the samples executed
"within the container where you pu
lan to test this in a testrun of 1 hour:
>
> Testplan
> + Thread Group (Number of Threads:50, Loop Count: Forever, 1 Hour run via
> Scheduler)
> + HTTP Request (with Follow Redirects, I know this request gets an 403
> which is followed, so in fact two requests are done)
>
1 - 100 of 101 matches
Mail list logo
