jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Jung <rainer.j...@kippdata.de>
Subject Re: svn commit: r1723411 - in /jmeter/trunk: bin/jmeter.properties src/core/org/apache/jmeter/reporters/Summariser.java
Date Thu, 07 Jan 2016 04:29:46 GMT
Am 07.01.2016 um 04:05 schrieb sebb:
> On 6 January 2016 at 21:03,  <pmouawad@apache.org> wrote:
>> Author: pmouawad
>> Date: Wed Jan  6 21:03:36 2016
>> New Revision: 1723411
>>
>> URL: http://svn.apache.org/viewvc?rev=1723411&view=rev
>> 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)

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

Regards,

Rainer

Mime
View raw message