An Oracle blog about Solaris

dtrace profiling

Chris Beal
Senior Principal Software Engineer

DTrace never fails to impress me in it's ability to simply find the answer to a technical question. My only problem is remembering the syntax, so I though I'd blog it here.

I could see from mpstat my CPU it was all being consumed in userland, so this simple dtrace command helped identify the culperit.

# dtrace -n 'profile-1001 /arg1/{@[execname, ustack()]=count()}END{trunc(@,10)}'

Showed me the top 10 stacks found, aggregated by process name too. It showed me in my case that pkgrecv was taking the CPU and it was infact the libcurl part..

Useful information for me

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.