Looping the monitor results listener - best way?
Hi, I've set up a simple test plan to see how the monitor results listener works based on the example online documentation (http://jakarta.apache.org/jmeter/usermanual/build-monitor-test-plan.html). At first I couldn't work out why I could only get the health tab showing green but no data on the peformance tab. I realised that the monitor thread group wasn't looping thus I was only ever getting one sample in the results. So is it better to have the monitor results thread group loop or put the elements of the thread group into a single loop controller? I can't really see a difference at the minute. However, for the future I think I'll want the monitor thread group to only run whilst another thread group in the same test plan is running i.e. in my test plan I have two thread groups, one for multiple threads completing actions to put load on my application; the other with a single thread to house the monitor results listener. Any advice is appreciated. Cheers -- View this message in context: http://www.nabble.com/Looping-the-monitor-results-listener---best-way--tp16979974p16979974.html Sent from the JMeter - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Looping the monitor results listener - best way?
if you want the monitor to only run during the stress test, just set the iteration and delay so it roughly matches the duration of the test. peter On Wed, Apr 30, 2008 at 6:50 AM, efj [EMAIL PROTECTED] wrote: Hi, I've set up a simple test plan to see how the monitor results listener works based on the example online documentation (http://jakarta.apache.org/jmeter/usermanual/build-monitor-test-plan.html). At first I couldn't work out why I could only get the health tab showing green but no data on the peformance tab. I realised that the monitor thread group wasn't looping thus I was only ever getting one sample in the results. So is it better to have the monitor results thread group loop or put the elements of the thread group into a single loop controller? I can't really see a difference at the minute. However, for the future I think I'll want the monitor thread group to only run whilst another thread group in the same test plan is running i.e. in my test plan I have two thread groups, one for multiple threads completing actions to put load on my application; the other with a single thread to house the monitor results listener. Any advice is appreciated. Cheers -- View this message in context: http://www.nabble.com/Looping-the-monitor-results-listener---best-way--tp16979974p16979974.html Sent from the JMeter - User mailing list archive at Nabble.com. - 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]
Re: Looping the monitor results listener - best way?
Peter Lin wrote: if you want the monitor to only run during the stress test, just set the iteration and delay so it roughly matches the duration of the test. OK thanks On a separate note - is there a way I can save the monitor results performance data? I've added a simple data writer but that only seems to record the HTTP request to the tomcat status servlet, rather than showing any response data - memory, load, thread etc. Much like the other listeners I'd like to save the data to a file to then be able to work with the raw data, or even reopen it via jmeter to look at an old peformance graph. Owning up I'm using jmeter 2.0.0 at the minute, so apologies if this functionalilty is in a newer release - we're moving to the latest release soon. Elliott. -- View this message in context: http://www.nabble.com/Looping-the-monitor-results-listener---best-way--tp16979974p16981573.html Sent from the JMeter - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
