Dear Felix, Currently have the following listeners:
1. Summary report 2. Aggregate report 3. View results tree In Constant timer, the value for 'Thread Delay' is set to 300 ms Thank You Jigi From: Felix Frank-2 [via JMeter] [mailto:[email protected]] Sent: Wednesday, June 22, 2011 3:54 AM To: Jeegnesh Sheth Subject: Re: determining ramp-up period On 06/22/2011 03:21 AM, jsheth wrote: > ERROR - jmeter.engine.StandardJMeterEngine: Uncaught exception: > java.lang.OutOfMemoryError: GC overhead limit exceeded Your threads consume too much memory. Beware of Listeners like View Result Tree, Aggregate Report etc. Try and make do with the Summary Report. You can save memory by adhering to http://jakarta.apache.org/jmeter/usermanual/best-practices.html#lean_mea n > 200 threads and 200 ramp up period results in 500 server error I guess your server cannot handle that load. Are you using timers? How much work does each Thread induce? Cheers, Felix --------------------------------------------------------------------- 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 below: http://jmeter.512774.n5.nabble.com/determining-ramp-up-period-tp4512401p 4513251.html To unsubscribe from determining ramp-up period, click here <http://jmeter.512774.n5.nabble.com/template/NamlServlet.jtp?macro=unsub scribe_by_code&node=4512401&code=anNoZXRoQHNyYy1zb2x1dGlvbnMuY29tfDQ1MTI 0MDF8NTUxNTAwNjA2> . -- View this message in context: http://jmeter.512774.n5.nabble.com/determining-ramp-up-period-tp4512401p4514034.html Sent from the JMeter - User mailing list archive at Nabble.com.
