Remove as many listeners as possible - indeed you can remove them all if you are using the -l flag. Use CSV output unless you really need the XML output.
As to GUI classes in non-GUI mode - yes, JMeter does load some GUI classes, because the XML aliases need to be defined for the GUI entries in the JMX files. Also JMeter startup searches all the archives in lib/ext for various interfaces during startup; this means that the GUI classes are loaded. I'm not sure if it would be possible to avoid loading the GUI classes without major restructuring. But it should be possible - if rather tedious - to rearrange the code to remove any unnecessary initialisation of Java AWT/Swing classes in non-GUI mode. S. On 21/08/07, chris <[EMAIL PROTECTED]> wrote: > hi, > > for our tests, we are running several jmeter testplans in non-gui-mode > (currently 6 jmeters at the same time) on a solaris system. each jmeter > needs up to 500 mb memory size. as we want to start more than 6 jmeter at > the same time... is it possible to reduce memory? > > we have already experimented with JVM options (xmx, xms,...), which brought > us some improvements by reducing memory usage. > > furthermore, we noticed that when running jmeter in non-gui mode on solaris, > we always get following message on standard-output: Java Accessibility > Bridge for GNOME loaded. why is that? does jmeter load GUI classes in > non-gui-mode? > > greets, > chris > > > > > --------------------------------------------------------------------- > 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]
