(Make sure you read the "Dimensional Analysis" aside) A hard disk is built out of circular surfaces called platters that rotate at rates measured in "rotations per minute". For example if a drive has 10,000 RPMs, i.e. it carries out 10000 rotations per minute, then it would carry out \(\frac{10000}{60} = \frac{1000}{6}\) rotations per second. This means then that it takes \(\frac{6}{1000}\) seconds, or 6 milliseconds, for a single rotation. How long would a rotation take if the drive speed was 15,000 RPMs?
Note this important fact: A drive rotation takes milliseconds, not microseconds. If you have to wait for the drive to do a full rotation to get to your data, thatβs a lot of time to a CPU.
Imagine we are in the situation described in figure 37.3 on the left side. Assume the arm moves to the outer circle, and it takes 2ms for that to happen. Also assume that the rotation of the disk is 10,000RPMs, so 6ms for a full rotation. Which sector would we be able to read at that moment?
The sector numbering on the boundaries between tracks is arranged so that if the arm is at the "last sector" of one track and it were to move to the next track, it would be at the "first sector" of that track, after accounting for the actual disk rotation in the meantime. This way reading consecutive sectors can continue to be fast even when switching tracks.
The Baracuda hard disk has a rotational speed of 7,200 RPMs, which translates to 8.33 milliseconds per rotation, or an average rotation time of about 4.17 ms. It also has an average seek time for 9ms, for a total time spend on rotation and seek equal to 13.17ms on average. With a transfer rate of 105MB per second, how much data do we need to transfer in order for the transfer time to equal this combined seek and rotation time?
Optional read: all of chapter 38 on RAID. The topic here is putting together multiple disks and storing information in multiple disks and in various fashions, with the intent to produce a faster and more reliable system (e.g. even if one drive goes bad, your data is not lost). Thereβs a lot of cool details there, but we wonβt be covering them in class.