Hi Andrey,
This has been discussed in a previous thread, see:
http://mail-archives.apache.org/mod_mbox/jmeter-dev/201404.mbox/%3CCAOGo0VaiM=TdW_Fj9fE1De4W8jao8ox5ELTAFVHTyN=5SY0d+Q@mail.gmail.com%3E
I think it is agreed upon by PMC members, changing this just breaks some
Tests that need to be fixed.
--
Regards.
Philippe M.
Ubik-Ingénierie
UBIK LOAD PACK Web Site <http://www.ubikloadpack.com/>
UBIK LOAD PACK on TWITTER <https://twitter.com/ubikloadpack>
On Fri, Sep 26, 2014 at 12:37 PM, Andrey Pokhilko <apc4@ya.ru> wrote:
> Hi team,
>
> Since I started developing JMeter plugins I faced one issue and after
> five years it is still the most frequent request from users: "why JTL
> does not contain active threads info?". Five years I've been answering
> that they should put
> jmeter.save.saveservice.thread_counts=true in their jmeter.properties.
>
> It is obvious that recording current level of active threads is very
> important for JMeter. Every analysis session starts from looking at
> active threads dynamics. Maybe it's time to enable it by default for
> everyone? It will just add couple more columns to CSV JTL.
>
> --
> Andrey Pokhilko
>
>
<http://twitter.com/ubikloadpack>
|