There are options for minimising the amount of data stored, such as: Use csv format Only log the data you actually need by setting options in the properties (these are well documented in the file itself).
But this will only improve things up to a point, ultimately if your tests are making large numbers of requests then you will have large numbers of results. The solution is to aggregate the data after the test run is complete. One quick option to do this is to write a simple awk script; you could even get a bit clever and pass in the total row count of the file which would allow the aggregation to be dynamic (ie. instead of grouping by every 15 lines it would group by every n lines where n is a calculated value based on how many rows there are). The nice thing about using something like awk is you can very easily wrap the whole process in a shell script (running jmeter and processing the results) and then everything is automated. Perl is also nice for this sort of thing but my preferred solution is to import the data to a database and use queries to reduce the output as this comes with a number of rather useful additional benefits (trending of results, comparisons, etc.) but then this option is a little more work to setup. On 17 Jun 2012, at 23:27, Shay Ginsbourg wrote: > Hi, > > What should be done in order to reduce the file size of the JTL results > while running Jmeter CMD ? > > The problem is that after a meaningful long run, we get over 20 GB, which > is way too much of a file. > > regards, > Shay --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
