Robert S. Horrigan wrote:
> Does anyone have any recommendations on how to capture using DTrace?
>
>>
>> Basically our client is tuning a Web Server 7 instance, and theApp team has
>> asked the sys admin to
>> observe the Acceptor threads. They want to see how many they have, how
>> many are active, what those are doing, and how many are left available.
>> I gave them the following Dtrace one-liners, and they said that it was
>> close, but not what they
>> wanted.
maybe if they told what was missing from the information DTrace gave you,
you'd be able to improve on the scripts?
>>
>> ?dtrace -n 'fbt:ip:tcp_acceptor_hash_*: / pid == <pid of jvm> /
>> {
>> printf("\n%s[%d]\t %s \t %
>> s",execname,pid,probefunc,probename);}'
>>
>> ?dtrace -n 'fbt:ip:tcp_acceptor_hash_*: / pid == <pid of jvm> /
>> { @num[probefunc] = count(); }'
>>
>> I also said he maybe able to get some information of the TCP stack with
>>
>> ndd -get /dev/tcp tcp_acceptor_hash
>>
>> But the sys admin didn't think that info helped.
same applies here. "doesn't help" is an insufficient problem description, IMO.
Michael
--
Michael Schuster http://blogs.sun.com/recursion
Recursion, n.: see 'Recursion'
_______________________________________________
dtrace-discuss mailing list
[email protected]
