fddist(1m) USER COMMANDS fddist(1m)NAME
fddist - file descriptor usage distributions. Uses DTrace.
SYNOPSIS
fddist [-r|-w]
DESCRIPTION
This prints distributions for read and write events by file descriptor, by process. This can be used to determine which file descriptor a
process is doing the most I/O with.
Since this uses DTrace, only users with root privileges can run this command.
OPTIONS -r reads only
-w writes only
EXAMPLES
Sample both read and write activity,
# fddist
Sample reads only,
# fddist -r
FIELDS
EXEC process name
PID process ID
value file descriptor
count number of events
BASED ON
/usr/demo/dtrace/lquantize.d
DOCUMENTATION
DTrace Guide "Aggregations" chapter (docs.sun.com)
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
fddist will sample until Ctrl-C is hit.
SEE ALSO dtrace(1M)version 0.70 Jun 08, 2005 fddist(1m)
Check Out this Related Man Page
bitesize.d(1m) USER COMMANDS bitesize.d(1m)NAME
bitesize.d - analyse disk I/O size by process. Uses DTrace.
SYNOPSIS
bitesize.d
DESCRIPTION
This produces a report for the size of disk events caused by processes. These are the disk events sent by the block I/O driver.
If applications must use the disks, we generally prefer they do so sequentially with large I/O sizes, or larger "bites".
Since this uses DTrace, only users with root privileges can run this command.
EXAMPLES
Sample until Ctrl-C is hit then print report,
# bitesize.d
FIELDS
PID process ID
CMD command and argument list
value size in bytes
count number of I/O operations
NOTES
The application may be requesting smaller sized operations, which are being rounded up to the nearest sector size or UFS block size.
To analyse what the application is requesting, DTraceToolkit programs such as Proc/fddist may help.
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
bitesize.d will sample until Ctrl-C is hit.
AUTHOR
Brendan Gregg [Sydney, Australia]
SEE ALSO iosnoop(1M), seeksize(1M), dtrace(1M)version 1.00 Jun 15, 2005 bitesize.d(1m)
I have a comma delimited file that sometimes has addresses details in. The problem is that the address detail can be seen as:
"Sample House, Sample Road". When I run a script specifying the file is comma delimited I would like it to ignore comma's that are in between speech marks.
Is this... (2 Replies)
hi gurus,
i am new to the AIX 5.3, if some one can provide the document related to the full command list with help, and other system admin related docs, it would be very helpful for me.
With Best Regards
Deepak (1 Reply)
Herez the question,
In a process which writes into file FILE1 with descriptor
fHandler1 and it is run as a background process
where would statements be directed
when stderr descriptor is used.
fprintf(stderr,"some message\n");
assume that session from which it is run is terminated and... (3 Replies)
Hi,
I want to write a script with dtrace to count the number of read and write from and to a file. I use this for reading:
dtrace -n 'syscall::read:entry { @ = count(); }'
but it doesn'f give me a single answer. The result is always increasing.
:wall:
Please use next time
code tags... (0 Replies)
Hello -
I have a requirement to get the Memory(Xmx) and the activity name using it.
Sample input info :
1502 02:57 /bin/sh /opt/rather/bar/deploy/bar_run.sh
1545 02:57 java -Drather.repository=/opt/rather/bar/deploy/JobSyng_Barol_Count/JobSyng_Barol_Count/../lib -Xms1024M... (3 Replies)