Hi, I guess it might be a problem for users which have big scripts. If that's reproducible - open a Bugzilla with sample files.
To be honest, the largest script I have ever had was around 1MB. I am not sure what I miss, but you may do some work to make it smaller (until a fix will be available). General Ideas: 1. Use config elements 2. Use same config elements for group of samplers and remove duplications. 3. Move data-sets outside the script file itself. 4. Remove disabled objects from the script. 5. Use Module controller. Can you share what's making your script file so big? or you are just asking a theoretical question?.. Best, Shmuel Krakower. www.Beatsoo.org - re-use your jmeter scripts for application performance monitoring from worldwide locations for free. On Mon, Dec 17, 2012 at 1:38 PM, Shay Ginsbourg <[email protected]>wrote: > Indeed, here are my findings, as follows: > > Opening a 1 MB JMX with Jmeter 2.8 (regardless of the HW > specification) is under 5 seconds, either on a Linux or a Windows > system. > With 2 MB file size, the user would have to wait under 10 seconds. > However, with 5 MB, the user would have to wait approximately 200 > seconds (over 3 minutes!) just to have Jmeter 2.8 open the JMX. > > Are those measurements known to all? > > Can the simple operation of file opening be optimized? > > > > > > > On Mon, Dec 17, 2012 at 12:51 AM, Stott, Charlie <[email protected]> wrote: > > > > You have asked an entirely subjective question. > > > > Perhaps you could publish your own findings and start a discussion, > rather > > than asking us all to run experiments for you. Clearly it is something > you > > think is an issue, but it is apparently not so to others. > > > > Charlie > > > > > -----Original Message----- > > > From: Shay Ginsbourg [mailto:[email protected]] > > > Sent: Sunday, 16 December 2012 6:53 PM > > > To: JMeter Users List > > > Subject: Re: JMX file->open duration > > > > > > Because I suspect it to be extremely non-linear, and increase to an > > > unacceptable time duration as a function of the file size. > > > > > > > > > > > > > > > On Sun, Dec 16, 2012 at 10:29 AM, Shmuel Krakower <[email protected]> > > > wrote: > > > > > > > > Why does it matter? > > > > On Dec 16, 2012 10:16 AM, "Shay Ginsbourg" <[email protected]> > > > wrote: > > > > > > > > > Hi, > > > > > What is the expected normal time duration of JMX file open > > > > > operation, where the JMX file size is 1MB, 2MB, 5MB ? > > > > > Any ideas? > > > > > thanks, > > > > > Shay > > > > > > > > > > > -------------------------------------------------------------------- > > > > > - To unsubscribe, e-mail: [email protected] > > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Regards, > > > > > > > > > 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. > > > > > > --------------------------------------------------------------------- > > > 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] > > > > > -- > > Regards, > > > 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. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
