iofileb.d(1m) [mojave man page]

iofileb.d(1m)							   USER COMMANDS						     iofileb.d(1m)

NAME

       iofileb.d - I/O bytes by file and process. Uses DTrace.

SYNOPSIS

       iofileb.d

DESCRIPTION

       This  prints  a	summary  of  requested	disk  activity	by pathname, providing totals of the I/O events in bytes. It is a companion to the
       iofile.d script - which prints in terms of I/O wait time, not bytes.  I/O wait time  is	a  better  metric  for	understanding  performance
       issues.	Both disk and NFS I/O are measured.

       Since this uses DTrace, only users with root privileges can run this command.

EXAMPLES

       Sample until Ctrl-C is hit then print report,
	      # iofileb.d

FIELDS

       PID    process ID

       CMD    process name

       KB     kilobytes of disk I/O

       FILE   file pathname

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

       iofileb.d will sample until Ctrl-C is hit.

SEE ALSO

       iofile.d(1M), iosnoop(1M), dtrace(1M)

version 1.00							   Feb 20, 2006 						     iofileb.d(1m)

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)