dtrace profiling


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



Comments:

Post a Comment:
Comments are closed for this entry.
About

Chris W Beal

Search

Archives
« April 2014
MonTueWedThuFriSatSun
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
    
       
Today