Just append the files together and then sort them by date/time.
This assumes that all the test plans write the same columns into the CSV files. This is probably easiest if the timestamps are written in the default "ms" format; if not, use a format that sorts properly (e.g. yyyy-MM-dd hh:mm:ss) S. On 21/05/07, Adamo, Vince <[EMAIL PROTECTED]> wrote:
Let me try this again.... In a recent reply to the message "Re: STOP SENDING HTTP REQUEST" the comment was made: "If that does not help, then run the test on each node in non-GUI mode, using CSV output, and then combine the results for further analysis if required." Can someone provide an explanation on how to accomplish this? I have been unsuccessful in configuring the distributed nodes to write local data files (using non-GUI mode and the Simple Data Writer) that can be merged. Thanks, Vince -----Original Message----- From: Adamo, Vince [mailto:[EMAIL PROTECTED] Sent: Monday, May 14, 2007 2:22 PM To: [email protected] Subject: Merging result files from remote servers The JMeter FAQ includes the following in the response to the question "How to do remote testing the 'proper way'": "Running JMeter in non-GUI (batch) mode is preferable, as this uses far fewer resources. The output log files can be merged after the test run and used to create overall test statistics. (CVS files can just be appended to each other; XML output files need a bit of editting to maintain well-formedness.)" This implies that there is a way to configure the JMeter servers to write result data to local files and then these files can be copied and merged after the test run completes. Is this a correct interpretation? If so, what is unclear in any documentation I've read so far, is how I would configure the remote servers to accomplish this. I am running version 2.2 in non-GUI mode (using the JMeter ant task) with two remote servers and have been unable to determine how to develop a test script or modify the jmeter.properties file to make this happen. In all cases it appears results are being returned to the client, where data is then written to a result file. Thanks, Vince --------------------------------------------------------------------- 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]
