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)
Check Out this Related Man Page
seeksize.d(1m) USER COMMANDS seeksize.d(1m)NAME
seeksize.d - print disk event seek report. Uses DTrace.
SYNOPSIS
seeksize.d
DESCRIPTION
seeksize.d is a simple DTrace program to print a report of disk event seeks by process.
This can be used to identify whether processes are accessing the disks in a "random" or "sequential" manner. Sequential is often desirable,
indicated by mostly zero length seeks.
Since this uses DTrace, only users with root privileges can run this command.
EXAMPLES
Sample until Ctrl-C is hit then print report,
# seeksize.d
FIELDS
PID process ID
CMD command and argument list
value distance in disk blocks (sectors)
count number of I/O operations
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
seeksize.d will sample until Ctrl-C is hit.
AUTHOR
Brendan Gregg [Sydney, Australia]
SEE ALSO iosnoop(1M), bitesize.d(1M), dtrace(1M)version 0.95 May 14, 2005 seeksize.d(1m)
Amazing but true...
tDacjrSCeq4
More details: Unusual disk latency : Brendan Gregg
Now I know why everything takes longer when I crank up the tunes. :eek: Oh well, it's nothing that a good set of headphones can't cure. (1 Reply)
I am trying to analyse a large file of sequencing data, example of first 10 lines below,
@HWUSI-EAS656_0044_FC:7:1:2447:1039#GCAATT/1
GNCTATGGCTTGCCGGGCTCAGGGAAGACAATCATAGCCATGAAAATCATGGAAAAGATCAGAAAAACATTTCAA
+HWUSI-EAS656_0044_FC:7:1:2447:1039#GCAATT/1... (1 Reply)
When I issue the du -sg from root to get the overall size of used disk on my AIX 6100-04 server I get back a size larger then my disk. From what I have read it may be adding the size of all linked directories. Is there a command to get the true disk useage or a switch for du to not count links... (3 Replies)
I have a file that reports the size of disks GB's or TB's - I need the file to report everything in MB's. Here is an extract of the file - the last column is the disk size.
19BC 2363 20G
1AA3 2363 2.93T
1A94 2363 750G
Whenever I come across a G I want to delete the G and multiply by... (2 Replies)
Hi,
We have hundreds of c codes for which we need to identify and analyse all the if , nested if and while conditions used in code.. is thr any tool to do that. All we is like index (like 1.2.1.3 in case of nested if)and the corresponding code (may be wrriten in a table/file).
Thanks..! (2 Replies)