jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Philippe Mouawad <>
Subject Re: svn commit: r1723411 - in /jmeter/trunk: bin/ src/core/org/apache/jmeter/reporters/
Date Thu, 07 Jan 2016 20:40:05 GMT
On Thu, Jan 7, 2016 at 5:29 AM, Rainer Jung <> wrote:

> Am 07.01.2016 um 04:05 schrieb sebb:
>> On 6 January 2016 at 21:03,  <> wrote:
>>> Author: pmouawad
>>> Date: Wed Jan  6 21:03:36 2016
>>> New Revision: 1723411
>>> URL:
>>> Log:
>>> [Bug 55512] Summariser should be enabled by default in Non GUI mode
>>> Restore 30 seconds as interval
>> -1
>> I don't agree with this for two reasons:
>> 1) it's nothing to do with enabling the the Summariser, so would need
>> a different bugzilla (if agreed)
If you read the bugzilla, I asked in the 3rd comment about this change to
30s and did it then. So it is in the bugzilla.

> <Nitpicking>That change from 3 minutes to 30 seconds happened back in 2013
> and would have needed a different BZ by then. It was then released. One
> could thus argue, that your change from 30 seconds back to 3 minutes would
> have needed a BZ</Nitpicking>
> 2) The interval is far too short as a default; it will cause log files
>> to be much longer.
> Since the value is configurable, it is a question about the best default.
> IMHO the best use case of the summariser is for human feedback during the
> test run. All other test analysis is better done based on the log protocol,
> reporting etc. For this live feedback I personally prefer a cycle where I
> don't have to wait so long. So I really liked the 30 seconds and for me 3
> minutes would be far too long.
I Agree with Rainer.
Lot of people do short test to check the Non Gui setup and want to see
results rapidly. Setting it to 180s might not show them anything, not
making them aware that this feature exists.
We do a lot of Huge Load Tests with 30s interval and the impact on log
files is nothing compared to the size of output files, besides it is very
useful as you detect much earlier any issue in application behaviour and
can look at it.

> Regards,
> Rainer

Philippe Mouawad.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message