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]
