Sponsored Content
Full Discussion: I/O performance
Top Forums UNIX for Advanced & Expert Users I/O performance Post 302088224 by izy100 on Sunday 10th of September 2006 01:10:43 PM
Old 09-10-2006
If you are using Solaris 10, you can use the iosnoop command that is built with DTrace. Search google for the iosnoop script.
It is able to break down the IO per binary.
 

7 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Performance

Hello, i have changed a slow server with Solaris 7 to a bigger one with Solaris 8 (Sun Ultra 2). Now i have a real bad performance problem (only CPU). Solaris 7 ran with standard FTP and Samba 2.0.7. The new machine is running ProFTP and Samba 2.0.9. There are a lot of NFS Shares and... (5 Replies)
Discussion started by: olso
5 Replies

2. UNIX for Advanced & Expert Users

performance

Hi, 1-in vmstat commande line, in reply, which column is the more important to look and verify if server is very slow ? 2-how can I see how many sessions are opened with the same login ? Many thanks before. (2 Replies)
Discussion started by: big123456
2 Replies

3. UNIX for Advanced & Expert Users

performance

Hi, I have this on a AIX UNIX machine : ps aux| head -20 USER PID %CPU %MEM SZ RSS TTY STAT STIME TIME COMMAND root 516 23.7 0.0 12 15808 - A 19:38:15 903:13 wait root 774 23.7 0.0 12 15808 - A 19:38:15 902:13 wait root 1290 23.6 0.0 ... (2 Replies)
Discussion started by: big123456
2 Replies

4. UNIX for Advanced & Expert Users

performance issue

Hi, on a linux server I have the following : vmstat 2 10 procs memory swap io system cpu r b w swpd free buff cache si so bi bo in cs us sy id 0 4 0 675236 39836 206060 1617660 3 3 3 6 8 7 1 1 ... (1 Reply)
Discussion started by: big123456
1 Replies

5. News, Links, Events and Announcements

Announcing collectl - new performance linux performance monitor

About 4 years ago I wrote this tool inspired by Rob Urban's collect tool for DEC's Tru64 Unix. What makes this tool as different as collect was in its day is its ability to run at a low overhead and collect tons of stuff. I've expanded the general concept and even include data not available in... (0 Replies)
Discussion started by: MarkSeger
0 Replies

6. Solaris

best way and best performance

Hi all, I have two storadge 3510 Fc .. with 12 disks 146Gb ..total 1752Gb each storadge. I need to use about 1.4 Tb of it. and want RAID1 .. I need 13 mount points .. So question: for best performance and redundjancy how I must do it. create 13 logical drives on each stordge with same size... (1 Reply)
Discussion started by: samar
1 Replies

7. UNIX for Dummies Questions & Answers

Performance issue

hi I am having a performance issue with the following requirement i have to create a permutation and combination on a set of three files such that each record in each file is picked and the output is redirected in a specific format but it is taking around 70 odd hours to prepare a combination... (7 Replies)
Discussion started by: mad_man12
7 Replies
iosnoop(1m)							   USER COMMANDS						       iosnoop(1m)

NAME
iosnoop - snoop I/O events as they occur. Uses DTrace. SYNOPSIS
iosnoop [-a|-A|-Deghinostv] [-d device] [-f filename] [-m mount_point] [-n name] [-p PID] DESCRIPTION
iosnoop prints I/O events as they happen, with useful details such as UID, PID, block number, size, filename, etc. This is useful to determine the process responsible for using the disks, as well as details on what activity the process is requesting. Be- haviour such as random or sequential I/O can be observed by reading the block numbers. Since this uses DTrace, only users with root privileges can run this command. OPTIONS
-a print all data -A dump all data, space delimited -D print time delta, us (elapsed) -e print device name -i print device instance -N print major and minor numbers -o print disk delta time, us -s print start time, us -t print completion time, us -v print completion time, string -d device instance name to snoop (eg, dad0) -f filename full pathname of file to snoop -m mount_point mountpoint for filesystem to snoop -n name process name -p PID process ID EXAMPLES
Default output, print I/O activity as it occurs, # iosnoop Print human readable timestamps, # iosnoop -v Print major and minor numbers, # iosnoop -N Snoop events on the root filesystem only, # iosnoop -m / FIELDS
UID User ID PID Process ID PPID Parent Process ID COMM command name for the process ARGS argument listing for the process SIZE size of the operation, bytes BLOCK disk block for the operation (location. relative to this filesystem. more useful with the -N option to print major and minor num- bers) STIME timestamp for the disk request, us TIME timestamp for the disk completion, us DELTA elapsed time from request to completion, us (this is the elapsed time from the disk request (strategy) to the disk completion (iodone)) DTIME time for disk to complete request, us (this is the time for the disk to complete that event since it's last event (time between iodones), or, the time to the strategy if the disk had been idle) STRTIME timestamp for the disk completion, string DEVICE device name INS device instance number D direction, Read or Write MOUNT mount point FILE filename (basename) for I/O operation NOTES
When filtering on PID or process name, be aware that poor disk event times may be due to events that have been filtered away, for example another process that may be seeking the disk heads elsewhere. 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
iosnoop will run forever until Ctrl-C is hit. AUTHOR
Brendan Gregg [Sydney, Australia] SEE ALSO
iotop(1M), dtrace(1M) version 1.50 Jul 25, 2005 iosnoop(1m)
All times are GMT -4. The time now is 09:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy