On 28/09/2007, Sonam Chauhan <[EMAIL PROTECTED]> wrote: > Thanks for clearing that up Sebb. That's pretty smart behaviour in the > ResultCollector :-)
Essential behaviour, as it cannot invoke methods on objects that don't exist or write to a null file ;-) The "smart" bit is not creating the GUI... > The tests do appear to finish normally -- they return a 0 status. This generally means little for a Java program - and JMeter only calls exit() with a non-zero status code for some very serious errors. > However, instead of 54000 log entries, there will be only 2000-3000 and > the last log entry will be truncated and look something like this: > --------- > <sampleResult timeStamp="1190950064802" dataType="text" threadName="Load > Test Thread Group 1-203" label="Insert ... item number 9350743" > time="11687" r XML output requires more memory; if you don't need the additional data, I suggest you use CSV output instead. If you need the additional data for only a few samples, add Simple Data Writers for those only. > --------- > > I run many instances at the same time, and haven't made the change that > will generate separate 'jmeter.log' files, but no out of memory errors > appear on the console. > > Kind regards, > Sonam Chauhan > -- > Corporate Express Australia Ltd. > Phone: +61-2-93350725, Email: [EMAIL PROTECTED] > > -----Original Message----- > From: sebb [mailto:[EMAIL PROTECTED] > Sent: Friday, 28 September 2007 8:38 PM > To: JMeter Users List > Subject: Re: listener element overhead in non-GUI mode. > > The GUI parts of the listeners should not be instantiated in non-GUI > mode; the ResutCollector checks to see if there is a GUI (or an output > file) before doing any more processing. > > However, there will be a Result Processor for each Listener, so this > will waste some processing, but should not cause much memory overhead. > > I don't understand why the log-files are truncated - do the tests > finish normally? > > On 28/09/2007, Sonam Chauhan <[EMAIL PROTECTED]> wrote: > > Hello - > > > > > > > > Quick question on listener element overhead when running in non-GUI > > mode. > > > > > > > > I have a JMeter testcase that runs a fair bit of load (900 threads x > 30 > > loops per thread x 2 samplers = 54000 requests). This always runs in > > non-GUI mode. The max JVM heap memory allocated is about 1 GB. > However, > > I am seeing truncated logfiles when running the test, but no out of > > memory errors. > > > > > > > > Normally I add 'View Results Tree' and 'Assertion Results' listener > > element to all my tests. Should I remove them from this testcase? Do > > visually-oriented listener elements cause problem even when running > > under non-GUI mode? > > > > > > > > Kind regards, > > > > Sonam Chauhan > > > > -- > > > > Corporate Express Australia Ltd. > > > > Phone: +61-2-93350725, Email: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
