You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Nick Faiz <ni...@ce.com.au> on 2003/10/24 05:12:18 UTC
stress test techniques
Hi all,
I've been using JMeter for a project and we're about to go into our
final stress test.
I have two questions:
1. I have one test case, sitting beneath a simple controller, that
places particularly heavy load on the server. Is there a way to create a
more complex execution condition beyond simply using the `Once Only
Controller'? I'd like to, for example, execute this test three times per
hour within the same .jmx script.
2. One of our goals here is to conduct a 24 hour test; which puts me in
the position of calculating a large number of threads over this time period.
I've used the Gaussian Random Timer as a sanity check between requests, to
ensure there's no DOS, but is there a better way of planning a sustained
test over a large amount of time?
Cheers,
Nick
Regards,
Nick Faiz
B2B e-Commerce Developer
Corporate Express Australia Ltd.
Phone: +61-2-9335-0495, Fax: 9335-0753, Email: nickf@ce.com.au
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: stress test techniques
Posted by ms...@apache.org.
On 24 Oct 2003 at 13:12, Nick Faiz wrote:
> Hi all,
> I've been using JMeter for a project and we're about to go into our
> final stress test.
> I have two questions:
>
> 1. I have one test case, sitting beneath a simple controller, that
> places particularly heavy load on the server. Is there a way to create a
> more complex execution condition beyond simply using the `Once Only
> Controller'? I'd like to, for example, execute this test three times per
> hour within the same .jmx script.
throughput controller might do what you want. It allows you to specify how often certain parts
of your test are executed.
>
> 2. One of our goals here is to conduct a 24 hour test; which puts me in
> the position of calculating a large number of threads over this time period.
> I've used the Gaussian Random Timer as a sanity check between requests, to
> ensure there's no DOS, but is there a better way of planning a sustained
> test over a large amount of time?
How about the Throughput Timer?
-Mike
>
> Cheers,
> Nick
>
>
> Regards,
> Nick Faiz
> B2B e-Commerce Developer
> Corporate Express Australia Ltd.
>
> Phone: +61-2-9335-0495, Fax: 9335-0753, Email: nickf@ce.com.au
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
--
Michael Stover
mstover1@apache.org
Yahoo IM: mstover_ya
ICQ: 152975688
AIM: mstover777
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org