Thanks Sebb, that works. I have a question. I notice the XML file includes all the non-html resources (I have retrieve embedded resources checked in the samplers) but it does not add these to the response time for the transaction when it creates a report, it reports only the response time for the main transactions. So, my question is does the response time for the main transaction include the non-html resources?
sebb-2-2 wrote: > > On 14/08/2008, rmiller <[EMAIL PROTECTED]> wrote: >> >> OK, the file is XML, so I have a chance. >> >> Looks like what I have to do, to convert the file, is parse each line >> for >> the field names and values, and then write that to a CSV file? Is there >> a >> delimiter between records? > > You'll need to extract the data from the tags and attributes. > This may involve reading several lines. > When you have got the last bit of data for the sample, write the CSV line. > > If you know Perl or Python it should be pretty simple to do. > >> Are the fields documented somewhere? I'd be interested to understand >> more >> about this file. >> > > http://jakarta.apache.org/jmeter/usermanual/listeners.html#xmlformat2.1 > and > http://jakarta.apache.org/jmeter/usermanual/listeners.html#attributes > >> Thanks, >> Ron >> >> >> >> sebb-2-2 wrote: >> > >> > On 14/08/2008, rmiller <[EMAIL PROTECTED]> wrote: >> >> >> >> Hi All, >> >> >> >> I wrote the data from a Summary Report to disk. The resulting jtl >> file >> >> is >> >> 194 MB in size. But when I try to open the file in the Summary >> Report I >> >> get >> >> an Out of Memory error. I'm running this on a machine with Windows >> XP >> >> with 2 >> >> GB of RAM. I have increased the heap size to 1 GB (1024MB). >> >> >> >> Is there anything I can do to run this report? >> >> >> > >> > Is the JTL file CSV or XML format? >> > >> > The XML format is much more resource intensive to read, as currently >> > the whole file is read before it can be processed, whereas CSV is >> > processed a line at a time. >> > >> > If the file is XML, and you cannot re-run the test to generate CSV, >> > then one possible workround would be to convert the XML file to CSV >> > using something like Perl. >> > >> > The XML format is fairly simple so would not be too hard to convert. >> > >> >> Thanks, >> >> Ron >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/Summary-Report-Out-of-Memory-errot-tp18974134p18974134.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] >> > >> > >> > >> >> >> -- >> View this message in context: >> http://www.nabble.com/Summary-Report-Out-of-Memory-errot-tp18974134p18986555.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] > > > -- View this message in context: http://www.nabble.com/Summary-Report-Out-of-Memory-errot-tp18974134p18991462.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]
