1) why not, good idea, but only if we don't enable 2) 2) My proposal is just to make the default enable it instead of not, with jmeter properties.
Take a non gui load test, how to check overall state of your test? - You can grep on csv but it's more linux and it's external tool - summariser is good for this now say you're a beginner in jmeter, do you find it a good thing that when using non gui mode nothing is shown by default ? I don't. I remember when I started with it, I found the tip on summariser only weeks after using it on milamber blog :) Now about performance, it only does easy sums inside synched block, and the output which will be the most consuming happens every 10 seconds if we configure it like this. And you still have the option to disable it. Regards Philippe On Sunday, September 1, 2013, sebb wrote: > On 1 September 2013 21:08, Philippe Mouawad > <[email protected]<javascript:;>> > wrote: > > Hello, > > Opening discussion on dev list. > > > > For completeness, here is the description of the issue: > > >> I think this very useful option should be enabled by default to > encourage usage > >> of non gui mode and because it has very low impact on performances. > > Enabled by default - what does that mean? That it should be added to: > 1) GUI test plans? > 2) non-GUI runs? > > If 1) then I agree it might be useful to add it to some of the > templates, to encourage using it. > > If 2) then I disagree. > First off, I don't see how it encourages users to use non-GUI mode to > add it to non-GUI mode - which they must are already using. > > Also, I hope that the performance impact is low, but we should check > first before making such a change. > > I would prefer to see the documentation enhanced to more fully explain > the disadvantages of GUI mode, and point out how to make non-GUI mode > easier to use, e.g. by adding the Summariser. > -- Cordialement. Philippe Mouawad.
