Let's say you do something simple like double-clicking on the icon for a spreadsheet file. This simple act, on many computers, can take 20 or 30 seconds to complete, and all during that time the hard disk is churning away. The hard disk access light flickers and the drive might make a whirring, whizzing or high-pitched whining noise. If the mechanism in the drive is loud, you definitely know that something is going on!
In the article How Hard Drives Work, you can see that there is an arm that holds the read-write heads. This arm can move the heads to tracks near the hub or near the edge of the disk. A normal hard disk is 5 inches (12.5 cm) or so in diameter. This arm therefore can move about 2 inches across the face of the disk.
The speed with which this arm can move is astonishing. The arm is very light and its actuator is powerful and precise. The arm can slide across the face of the disk hundreds of times per second if it needs to.
If you think about how a speaker works, there is not much of a difference. A speaker is moving a lightweight cone back and forth hundreds of times per second to generate sound. As the arm moves back and forth rapidly, it sets up vibrations that our ears hear as sounds.
Why, when you click on a simple spreadsheet file, would the disk's heads have to move so much (20 or 30 seconds worth of movement sometimes)? There are three things that cause all the movement:
Altogether, clicking on a single icon may cause 40 or 50 megabytes of data to move between the drive and RAM, with the disk heads repositioning themselves thousands of times in the process. That is why you hear the drive "churning" - it's doing a lot of work!
- To start a spreadsheet application like Excel, the hard disk has to load the application itself along with a number of DLLs (Dynamic Link Libraries) that support the application. The total size of all these different files might be 10 to 20 megabytes, and the files are scattered all over the disk. Loading 20 megabytes of data takes a lot of time and requires the disk head to move thousands of time to retrieve all the pieces.
- The data file itself has to load. The operating system has to move the head to the drive's directory to find the folder, make sure the file name exists, and then discover the location of the file. Then the OS may need to read dozens of tracks scattered all of the drive to access the file.
- If the physical RAM is full, then during the loading process the OS will have to unload parts of physical RAM and save them to the paging file on the disk. So while the OS is trying to load the spreadsheet application and all the DLLs and the data file, it is at the same time trying to write millions of bytes of data to the paging file to make room for the new application. The drive head is moving all over the disk to accomplish these intermingled tasks. See Question 175 for details.