And you'll use even less memory if you run in non-GUI mode. No need to include any listeners if you add the -l flag (it will add one)
You can use -Jsummariser.name=myname to automatically write a summary to the log every 3 minutes. See jmeter.properties for more config options. We have run JMeter tests for a whole weekend this way. S. On Wed, 16 Mar 2005 09:25:12 -0500, Michael Stover <[EMAIL PROTECTED]> wrote: > You could probably go pretty far with just the aggregate report. It > probably the most memory friendly (will still run out eventually). > Since all listeners can save the raw data to file, you would still be > able to load the data later into the graph listener. > > -Mike > > On Wed, 2005-03-16 at 08:55, [EMAIL PROTECTED] wrote: > > I am running the aggregate report and indeed a graphical listener. > > > > I will try running the same tests with only the simple listener and see > > how that works. > > > > Thanks for the quick reply! > > > > Always, > > Vince > > > > > > > > > > > > Peter Lin <[EMAIL PROTECTED]> > > 03/16/2005 08:50 AM > > Please respond to "JMeter Users List" > > > > > > To: JMeter Users List <[email protected]> > > cc: > > Subject: Re: JMeter Consumming all Memory > > > > > > > > what listeners do you have in the test plan? > > > > if you plan to run a test plan for longer than 30minutes, you should > > use the simple listener to write the results to a file. If you use > > view result tree or any of the graphical listeners, it will > > eventually run out of memory. > > > > peter > > > > > > > > On Wed, 16 Mar 2005 08:43:57 -0500, [EMAIL PROTECTED] > > <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > I've been trying to use JMeter to run load tests but it seems that no > > > matter what heap size I give it, it gradually uses up all memory and > > gets > > > bogged down in garbage collects. > > > > > > I am using a series of HTTP Samplers to generate roughly 50 requests a > > > second (50 threads each generating 1 request a second). It will run > > > smoothly enough for 5 hours or so and then it will usually begin to > > become > > > unstable (requests taking longer and longer to complete, round trip > > times > > > spiking for no reason, etc...). > > > > > > I have tried to extend the heap size but it just seems to delay the > > point > > > at which everything goes heywire. > > > > > > Is it normal for JMeter to gradually use up all memory it has available? > > > > > > The only settings I've played with in the jmeter.bat file are the heap > > > size and I've tried using one of the concurrent garbage collect schemes. > > > > > > Any insight anyone might have would be very much appreciated. > > > > > > Sincerely, > > > Vince > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > -- > Michael Stover <[EMAIL PROTECTED]> > Apache Software Foundation > > > --------------------------------------------------------------------- > 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]
