My proposal is to stop the test at start of test. Would your comments still apply ?
Thanks On Wed, May 13, 2015 at 11:01 PM, chaitanya bhatt <[email protected] > wrote: > Instead of stopping the test, I would recommend that Jmeter stop recording > the results. There are many users who collect performance metrics from APM > tools like AppDynamics,Dynatrace, Wily etc. Proactively stopping the test > would be a bad idea for such users. These users do not rely on performance > metrics from Jmeter's JTL files. > > Jmeter should ideally stop recording logs or results upon reaching the disk > space threshold thereby conserving space. The tool should just be > generating load under this circumstance. > > Thoughts? > > Thanks > Chaitanya M Bhatt > http://www.performancecompetence.com > > On Wed, May 13, 2015 at 12:53 PM, Philippe Mouawad < > [email protected]> wrote: > > > Hello, > > > > What do you think of the following feature. > > > > Sometimes it happened to me to have a test fail at end due to not having > > enough disk space , so I lost the end of my test results. > > > > > > I was thinking of the following way to fix it : > > > > - Create a proprerty which contains the disk space required estimation > > - At start of test, listeners that need to write file check using > File > > or FileStore (JDK7) > > - If value is lower than expected size, they trigger end of test > > > > > > Do you think this is over engeneering ? or bad idea ? > > > > > > Thanks > > > > Regards > > > -- Cordialement. Philippe Mouawad.
