jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jsheth <>
Subject RE: determining ramp-up period
Date Wed, 22 Jun 2011 01:21:42 GMT
I would rather not have it that slow


I just ran it with 200 threads and 6000seconds ramp up time and I got 

ERROR - jmeter.engine.StandardJMeterEngine: Uncaught exception:
java.lang.OutOfMemoryError: GC overhead limit exceeded


200 threads and 200 ramp up period results in 500 server error


From: Barrie Treloar [via JMeter]
Sent: Tuesday, June 21, 2011 9:17 PM
To: Jeegnesh Sheth
Subject: Re: determining ramp-up period


On Wed, Jun 22, 2011 at 10:31 AM, jsheth <[hidden email]> wrote: 
> So for 200 threads I should set my ramp up time to be > 6000? 

Ramp up time = 6000 seconds. 
This will start a new thread, on average, every 6000/200 = 30 seconds 
where all threads will be running after 6000/60 = 100 minutes (or 1hr 
40 minutes). 

You sure you want it that slow? 

Just follow the formulate, 

   Ramp up Time / Threads = Start a thead every X seconds 

To work out what you should pick. 
e.g. 600 would mean 600/200 = start a thread every 3 seconds, which 
means 600/60 = 10 minutes to full capacity. 
This may also be too slow, but you can tweak and fiddle to see how the 
load impacts on your server. 

To unsubscribe, e-mail: [hidden email] 
For additional commands, e-mail: [hidden email] 


If you reply to this email, your message will be added to the discussion

To unsubscribe from determining ramp-up period, click here

View this message in context:
Sent from the JMeter - User mailing list archive at
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message