Hi,

Thanks for the reply.

Q: Is there a recommended configuration setting for opening large JTL files
within Jmeter ?

For example, while running a larger JTL (>> 10GB), a see that the java.exe
CPU is < 10% on Win7 task manager.

It takes much time to create just the Jmeter summary report on a i5 core
with 6 GB RAM.

Probably, the bottleneck is the speed of the hard-drive, but I'm wandering
if anything could be optimized at some level.

thanks,
Shay




On Mon, Jun 18, 2012 at 1:54 AM, oliver lloyd <[email protected]>wrote:

> 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]
>
>


-- 


Shay Ginsbourg

Regulatory & Testing Affairs Consultant


WWW.GINSBOURG.COM


Providing Regulatory, Medical & Performance Testing services since 2008:

* IEC 62304 Medical Device Software Life Cycle

* IEEE 829 Software Test Documentation

* ISO 14971 Medical Device Risk Management

* FDA 21 CFR Part 11 Software Validation

* IEC 60601-1:2005 3rd ED PEMS - Medical Electrical Equipment

* End-to-end verification, validation, and testing (VV&T)

* FDA and CE submissions

* Open source free testing tools implementation

* Functionality and regression testing

* Software Performance & Load testing

* Software Testing Advanced Automation

* Medical Software Verification & Validation

* Medical Device Verification & Validation

* Medical Device Regulatory Submission

* Organizational Regulatory Qualification


Formerly QA Manager of LoadRunner at Mercury Interactive


M.Sc. cum laude in Bio-Medical Engineering

M.Sc. in Mechanical Engineering



Work:   +972(0)3-5185873

Mobile:  +972(0)54-6690915


Email: [email protected]


Visit my personal page on LinkedIn at:
http://www.linkedin.com/in/shayginsbourg


Please consider your environmental responsibility before printing this
e-mail.

Reply via email to