Re: Thread top command

[Jean-Baptiste Onofré]

It makes sense. Let me experiment a bit more.

Thanks,
Regards
JB

On 10/17/2016 01:12 PM, Guillaume Nodet wrote:

Not sure, if we think those options are better than the default, we should
make them the default ones ;-)
The refresh rate of 128 ms is fine for debugging (and nicer because of the
fading display), but I's a bit CPU intensive, so I'm not sure it's really
worth it.  The refresh rate can be changed at runtime with '-' and '+'.
Also, in the informations showed by the command I pasted, some are not
really useful, but I guess it depends on the use case.
Anyway, I'm not sure it would be good to create an alias, I'd rather change
the default options.

2016-10-17 12:11 GMT+02:00 Jean-Baptiste Onofré :


Hi Guillaume,

thanks.

What do you think about an alias with the ttop proposed options ?

Regards
JB


On 10/17/2016 12:09 PM, Guillaume Nodet wrote:


I've just pushed a commit that adds a new ttop command that displays a
list
of threads.  Feel free to play with it.

I recommend the following command:


ttop


--stats=tid,name,state,waited_time,waited_count,blocked_time
,blocked_count,user_time,cpu_time,user_time_perc,cpu_time_
perc,lock_owner_id,lock_owner_name
--order=cpu_time --millis=128

It's using advanced jline stuff, so please give it a try on your usual
terminal/os and report any problems.

Cheers,
Guillaume



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com







--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Thread top command

[Guillaume Nodet]

Not sure, if we think those options are better than the default, we should
make them the default ones ;-)
The refresh rate of 128 ms is fine for debugging (and nicer because of the
fading display), but I's a bit CPU intensive, so I'm not sure it's really
worth it.  The refresh rate can be changed at runtime with '-' and '+'.
Also, in the informations showed by the command I pasted, some are not
really useful, but I guess it depends on the use case.
Anyway, I'm not sure it would be good to create an alias, I'd rather change
the default options.

2016-10-17 12:11 GMT+02:00 Jean-Baptiste Onofré :

> Hi Guillaume,
>
> thanks.
>
> What do you think about an alias with the ttop proposed options ?
>
> Regards
> JB
>
>
> On 10/17/2016 12:09 PM, Guillaume Nodet wrote:
>
>> I've just pushed a commit that adds a new ttop command that displays a
>> list
>> of threads.  Feel free to play with it.
>>
>> I recommend the following command:
>>
>>> ttop
>>>
>> --stats=tid,name,state,waited_time,waited_count,blocked_time
>> ,blocked_count,user_time,cpu_time,user_time_perc,cpu_time_
>> perc,lock_owner_id,lock_owner_name
>> --order=cpu_time --millis=128
>>
>> It's using advanced jline stuff, so please give it a try on your usual
>> terminal/os and report any problems.
>>
>> Cheers,
>> Guillaume
>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>



-- 

Guillaume Nodet

Red Hat, Open Source Integration

Email: gno...@redhat.com
Web: http://fusesource.com
Blog: http://gnodet.blogspot.com/

Re: Thread top command

[Jean-Baptiste Onofré]

Hi Guillaume,

thanks.

What do you think about an alias with the ttop proposed options ?

Regards
JB

On 10/17/2016 12:09 PM, Guillaume Nodet wrote:

I've just pushed a commit that adds a new ttop command that displays a list
of threads.  Feel free to play with it.

I recommend the following command:

ttop

--stats=tid,name,state,waited_time,waited_count,blocked_time,blocked_count,user_time,cpu_time,user_time_perc,cpu_time_perc,lock_owner_id,lock_owner_name
--order=cpu_time --millis=128

It's using advanced jline stuff, so please give it a try on your usual
terminal/os and report any problems.

Cheers,
Guillaume



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com