I use the Simple Data Writer Listener, set it to save only failing results to specific jtl in XML format with all data available. This way - if I want to understand what went wrong during a load test, I have all info at hand, opening it with the View Results Tree later.
Shmuel Krakower. www.Beatsoo.org - re-use your jmeter scripts for application performance monitoring from worldwide locations for free. On Wed, Jan 9, 2013 at 3:47 PM, Robin D. Wilson <[email protected]> wrote: > An alternative is to use those two listeners, but only capture "Errors". > I can't imagine any value (for analysis) of reviewing thousands of > "successful" request/responses (can you say data overload?)... But if you > check the little box on the listener to just capture errors, then those > listeners are quite useful. > > Of course, you have to make sure that your test returns an error when > something goes awry. You can use Assertions for this. In our tests, each > request has at least one assert associated with it, looking in the response > for some string that should be present if the request was successful, but > absent if it fails. This assures we get an error logged in the Tree > listener when a request does do what we expected it to do. > > -- > Robin D. Wilson > VOICE: 512-777-1861 > > > > On Jan 9, 2013, at 3:11 AM, Philippe Mouawad <[email protected]> > wrote: > > Hello, > No you don't need these 2 listeners for analysis with 100 threads and 2 > hours run. > > These 2 listeners are to be used during scripting debug with 1 to 5 users > max and with few seconds to very few minutes of run, once your script is > debugged and OK, > you must remove them and absolutely not use them during load test. > > With 100 threads, I doubt you really need distributed testing > Read this: > > - http://jmeter.apache.org/usermanual/best-practices.html > - http://www.ubik-ingenierie.com/blog/jmeter_performance_tuning_tips/ > > > RegardsPhilippe M. > > On Wed, Jan 9, 2013 at 10:10 AM, Niraj <[email protected]> wrote: > > > Then use non gui mode. But having these two listeners in your test plan > > will consumes lot's of memory. I am not sure why do you need both the > > listeners? Are you analyzing all the requests responses for 100 users? > > > > On Wed, Jan 9, 2013 at 2:34 PM, Srinivasa Tekkatte Shenoy < > > [email protected]> wrote: > > > >> I am already using distributed testing one master and 3 slaves. > >> > >> We need these two listeners for analysis. > >> > >> Thank You > >> > >> Regards > >> Shenoy > >> > >> -----Original Message----- > >> From: Niraj [mailto:[email protected]] > >> Sent: Wednesday, 9 January, 2013 5:02 PM > >> To: JMeter Users List > >> Cc: [email protected] > >> Subject: Re: JMeter out of memory > >> > >> View Results in Table and View Results in Tree listeners consumes lot's > >> of memory. Remove this two listeners and re-run the test again. > >> > >> If you are still facing the same issue then use distributed testing. > >> > >> On Wed, Jan 9, 2013 at 2:24 PM, Srinivasa Tekkatte Shenoy < > >> [email protected]> wrote: > >> > >>> Hi All, > >>> > >>> I am executing the JMeter for a script with 100 user threads for 2 > >>> hours duration and loop count set to Forever. Ramp up and ramp down in > >>> of total > >>> 100 users in one minute. > >>> > >>> The min and max Heap size of Jmeter.bat is set as 1GB. It cannot be > >>> increase to more. Whether any other way to increase the heap size. > >>> > >>> We currently have listeners for Summary Report, View Results in Table > >>> and View Results in Tree. > >>> > >>> I am getting out of memory error after 30minutes. Could you please > >>> let me know how to fix this. > >>> > >>> Thank You > >>> > >>> Regards > >>> Shenoy > >>> > >>> > >>> > >>> ------------------------------------------------------------------ > >>> - > >>> - > >>> DISCLAIMER: > >>> > >>> This e-mail (including any attachments) is for the addressee(s) only > >>> and may contain confidential information. If you are not the intended > >>> recipient, please note that any dealing, review, distribution, > >>> printing, copying or use of this e-mail is strictly prohibited. If you > >>> have received this email in error, please notify the sender > >>> immediately and delete the original message. > >>> MIMOS Berhad is a research and development institution under the > >>> purview of the Malaysian Ministry of Science, Technology and > >>> Innovation. Opinions, conclusions and other information in this e- > >>> mail that do not relate to the official business of MIMOS Berhad > >>> and/or its subsidiaries shall be understood as neither given nor > >>> endorsed by MIMOS Berhad and/or its subsidiaries and neither MIMOS > >>> Berhad nor its subsidiaries accepts responsibility for the same. All > >>> liability arising from or in connection with computer viruses and/or > >>> corrupted e-mails is excluded to the fullest extent permitted by law. > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > > > > -- > Cordialement. > Philippe Mouawad. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
