procsystime(1m) [osx man page]
procsystime(1m) USER COMMANDS procsystime(1m) NAME
procsystime - analyse system call times. Uses DTrace. SYNOPSIS
procsystime [-acehoT] [ -p PID | -n name | command ] DESCRIPTION
procsystime prints details on system call times for processes, both the elapsed times and on-cpu times can be printed. The elapsed times are interesting, to help identify syscalls that take some time to complete (during which the process may have slept). CPU time helps us identify syscalls that are consuming CPU cycles to run. Since this uses DTrace, only users with root privileges can run this command. OPTIONS
-a print all data -c print syscall counts -e print elapsed times, ns -o print CPU times, ns -T print totals -p PID examine this PID -n name examine processes which have this name EXAMPLES
Print elapsed times for PID 1871, # procsystime -p 1871 Print elapsed times for processes called "tar", # procsystime -n tar Print CPU times for "tar" processes, # procsystime -on tar Print syscall counts for "tar" processes, # procsystime -cn tar Print elapsed and CPU times for "tar" processes, # procsystime -eon tar print all details for "bash" processes, # procsystime -aTn bash run and print details for "df -h", # procsystime df -h FIELDS
SYSCALL System call name TIME (ns) Total time, nanoseconds COUNT Number of occurrences DOCUMENTATION
See the DTraceToolkit for further documentation under the Docs directory. The DTraceToolkit docs may include full worked examples with ver- bose descriptions explaining the output. EXIT
procsystime will sample until Ctrl-C is hit. AUTHOR
Brendan Gregg [Sydney, Australia] SEE ALSO
dtruss(1M), dtrace(1M), truss(1) version 1.00 Sep 22, 2005 procsystime(1m)
Check Out this Related Man Page
dapptrace(1m) USER COMMANDS dapptrace(1m) NAME
dapptrace - trace user and library function usage. Uses DTrace. SYNOPSIS
dapptrace [-acdeFlhoU] [-u lib] { -p PID | command } DESCRIPTION
dapptrace prints details on user and library function calls. By default it traces user functions only, options can be used to trace library activity. Of particular interest is the elapsed times and on cpu times, which can identify both function calls that are slow to complete, and those which are consuming CPU cycles. Since this uses DTrace, only users with root privileges can run this command. OPTIONS
-a print all details -b bufsize dynamic variable buffer size. Increase this if you notice dynamic variable drop errors. The default is "4m" for 4 megabytes per CPU. -c print function call counts -d print relative timestamps, us -e print elapsed times, us -F print flow indentation -l force printing of pid/lwpid per line -o print on-cpu times, us -p PID examine this PID -u lib trace this library instead -U trace all library and user functions EXAMPLES
run and examine the "df -h" command, # dapptrace df -h examine PID 1871, # dapptrace -p 1871 print using flow indents, # dapptrace -Fp 1871 print elapsed and CPU times, # dapptrace -eop 1871 FIELDS
PID/LWPID Process ID / Lightweight Process ID RELATIVE relative timestamps to the start of the thread, us (microseconds) ELAPSD elapsed time for this system call, us CPU on-cpu time for this system call, us CALL(args) function call name, with some arguments in hexadecimal DOCUMENTATION
See the DTraceToolkit for further documentation under the Docs directory. The DTraceToolkit docs may include full worked examples with ver- bose descriptions explaining the output. EXIT
dapptrace will run forever until Ctrl-C is hit, or if a command was executed dapptrace will finish when the command ends. AUTHOR
Brendan Gregg [Sydney, Australia] SEE ALSO
dappprof(1M), dtrace(1M), apptrace(1) version 1.10 May 14, 2005 dapptrace(1m)