Sponsored Content
Special Forums Hardware Filesystems, Disks and Memory Loud Sounds can slow down disk I/O Post 302287583 by Perderabo on Saturday 14th of February 2009 12:30:26 PM
Old 02-14-2009
Loud Sounds can slow down disk I/O

Amazing but true...



More details: Unusual disk latency : Brendan Gregg

Now I know why everything takes longer when I crank up the tunes. Smilie Oh well, it's nothing that a good set of headphones can't cure.
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Are there sounds in Mandrake

First of sll, i wan to apologize to all of the admin. or peoples who are noticing all of my posts today, Im at school and i really have nothing else to do, im in strudy hall and my teacher wont let me check my email, but any ways, i just remembered that I don't have any sounds in Mandrake like i... (4 Replies)
Discussion started by: LolapaloL
4 Replies

2. Ubuntu

Playing wav-file sounds.

I would like to be able to shell out to the command line and play sounds. After installing "sox" I can now do this using the play command. Is there a way to stop the playing once it starts? (5 Replies)
Discussion started by: newyorkpaulie
5 Replies

3. Solaris

Hard disk write performance very slow

Dear All, I have a hard disk in solaris on which the write performanc is too slow. The CPU , RAM memory are absolutely fine. What might be reason. Kindly explain. Rj (9 Replies)
Discussion started by: jegaraman
9 Replies

4. UNIX for Advanced & Expert Users

check if the disk is slow

Hi, we have some Oracle DBs on a AIX server. We have the following error messages : Warning: log write time 540ms, size 5444KB *** 2008-05-14 10:19:02.686 Warning: log write time 1470ms, size 5533KB Oracle in LGWR Is Generating Trace file with "Warning: Log Write Time 540ms, Size 5444kb"... (6 Replies)
Discussion started by: big123456
6 Replies

5. Solaris

V20z terribly loud - firmware update?

Hello there! I am familiar with Linux, FreeBSD, but relatively new to Solaris. Because I wanted to play a little with servers and networks, I got a used SunFire v20z with AMD Opteron processors and installed OpenIndiana 151a8 on top of that. This is the first machine of this kind I have ever... (1 Reply)
Discussion started by: guru987
1 Replies

6. AIX

IBM P730 running AIX 7.1 (8231-E2B) - Fans spinning loud/max rpm?

We have a IBM P730 machine running AIX 7.1 in a properly air cooled server room. Just recently the fans on the unit kicked into overdrive, they are very loud and spinning at max. Typically this happens when the server first boots then they normalize. However for some odd reason, they sound... (2 Replies)
Discussion started by: c3rb3rus
2 Replies
iotop(1m)							   USER COMMANDS							 iotop(1m)

NAME
iotop - display top disk I/O events by process. Uses DTrace. SYNOPSIS
iotop [-C] [-D|-o|-P] [-j|-Z] [-d device] [-f filename] [-m mount_point] [-t top] [interval [count]] DESCRIPTION
iotop tracks disk I/O by process, and prints a summary report that is refreshed every interval. This is measuring disk events that have made it past system caches. Since this uses DTrace, only users with root privileges can run this command. OPTIONS
-C don't clear the screen -D print delta times - elapsed, us -j print project ID -o print disk delta times, us -P print %I/O (disk delta times) -Z print zone ID -d device instance name to snoop (eg, dad0) -f filename full pathname of file to snoop -m mount_point mountpoint for filesystem to snoop -t top print top number only EXAMPLES
Default output, print summary every 5 seconds # iotop One second samples, # iotop 1 print %I/O (time based), # iotop -P Snoop events on the root filesystem only, # iotop -m / Print top 20 lines only, # iotop -t 20 Print 12 x 5 second samples, scrolling, # iotop -C 5 12 FIELDS
UID user ID PID process ID PPID parent process ID PROJ project ID ZONE zone ID CMD command name for the process DEVICE device name MAJ device major number MIN device minor number D direction, Read or Write BYTES total size of operations, bytes ELAPSED total elapsed times from request to completion, us (this is the elapsed time from the disk request (strategy) to the disk completion (iodone)) DISKTIME total times 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) %I/O percent disk I/O, based on time (DISKTIME) load 1 minute load average disk_r total disk read Kb for sample disk_w total disk write Kb for sample 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
iotop will run forever until Ctrl-C is hit, or the specified interval is reached. AUTHOR
Brendan Gregg [Sydney, Australia] SEE ALSO
iosnoop(1M), dtrace(1M) version 0.75 Oct 25, 2005 iotop(1m)
All times are GMT -4. The time now is 08:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy