Disk Drive Performance
Seek Time
The seek time (also called access time) describes the time taken to position the R/W heads across the platter with a radial movement (moving along the radius of the platter). In other words, it is the time taken to position and settle the arm and the head over the correct track. Therefore, the lower the seek time, the faster the I/O operation. Disk vendors publish the following seek time specifications:
- Full Stroke: The time taken by the R/W head to move across the entire width of the disk, from the innermost track to the outermost track.
- Average: The average time taken by the R/W head to move from one random track to another, normally listed as the time for one-third of a full stroke.
- Track-to-Track: The time taken by the R/W head to move between adjacent tracks.
Each of these specifications is measured in milliseconds. The seek time of a disk is typically specified by the drive manufacturer. The average seek time on a modern disk is typically in the range of 3 to 15 milliseconds. Seek time has more impact on the read operation of random tracks rather than adjacent tracks. To minimize the seek time, data can be written to only a subset of the available cylinders. This results in lower usable capacity than the actual capacity of the drive. For example, a 500 GB disk drive is set up to use only the first 40 percent of the cylinders and is effectively treated as a 200 GB drive. This is known as short-stroking the drive.
Rotational Latency
To access data, the actuator arm moves the R/W head over the platter to a particular track while the platter spins to position the requested sector under the R/W head. The time taken by the platter to rotate and position the data under the R/W head is called rotational latency. This latency depends on the rotation speed of the spindle and is measured in milliseconds. The average rotational latency is one-half of the time taken for a full rotation. Similar to the seek time, rotational latency has more impact on the reading/writing of random sectors on the disk than on the same operations on adjacent sectors.
Average rotational latency is approximately 5.5 ms for a 5,400-rpm drive, and around 2.0 ms for a 15,000-rpm (or 250-rps revolution per second) drive as shown here:
Average rotational latency for a 15,000 rpm (or 250 rps) drive = 0.5/250 = 2 milliseconds.
Data Transfer Rate
The data transfer rate (also called transfer rate) refers to the average amount of data per unit time that the drive can deliver to the HBA. It is important to first understand the process of read/write operations to calculate data transfer rates. In a read operation, the data first moves from disk platters to R/W heads; then it moves to the drive's internal buffer. Finally, data moves from the buffer through the interface to the host HBA. In a write operation, the data moves from the HBA to the internal buffer of the disk drive through the drive's interface. The data then moves from the buffer to the R/W heads. Finally, it moves from the R/W heads to the platters.
A converged network adapter (CNA) is a single network interface card (NIC) that contains both a Fibre Channel (FC) host bus adapter (HBA) and a TCP/IP Ethernet NIC. It connects servers to FC-based storage area networks (SANs) and Ethernet-based local area networks (LANs).
The CNA connects to the server via a PCI Express (PCIe) interface. The server sends both FC SAN and LAN and traffic to an Ethernet port on a converged switch using the Fibre Channel over Ethernet (FCoE) protocol for the FC SAN data and the Ethernet protocol for LAN data. The converged switch converts the FCoE traffic to FC and sends it to the FC SAN. The Ethernet traffic is sent directly to the LAN.
A converged network adapter (CNA) is a single network interface card (NIC) that contains both a Fibre Channel (FC) host bus adapter (HBA) and a TCP/IP Ethernet NIC. It connects servers to FC-based storage area networks (SANs) and Ethernet-based local area networks (LANs).
The CNA connects to the server via a PCI Express (PCIe) interface. The server sends both FC SAN and LAN and traffic to an Ethernet port on a converged switch using the Fibre Channel over Ethernet (FCoE) protocol for the FC SAN data and the Ethernet protocol for LAN data. The converged switch converts the FCoE traffic to FC and sends it to the FC SAN. The Ethernet traffic is sent directly to the LAN.
To calculate the IOPS range, use this formula: Average IOPS: Divide 1 by the sum of the average latency in ms and the average seek time in ms (1 / (average latency in ms + average seek time in ms).
Sample drive:
- Model: Western Digital VelociRaptor 2.5″ SATA hard drive
- Rotational speed: 10,000 RPM
- Average latency: 3 ms (0.003 seconds)
- Average seek time: 4.2 (r)/4.7 (w) = 4.45 ms (0.0045 seconds)
- Calculated IOPS for this disk: 1/(0.003 + 0.0045) = about 133 IOPS
As you can see, the values for each kind of drive don’t radically change from source to source.
Sources:
- http://blog.aarondelp.com/2009/10/its-now-all-about-iops.html
- http://www.yellow-bricks.com/2009/12/23/iops/
- http://www.tomshardware.com/forum/251893-32-raid-raid
To calculate the IOPS range, use this formula: Average IOPS: Divide 1 by the sum of the average latency in ms and the average seek time in ms (1 / (average latency in ms + average seek time in ms).
Sample drive:
- Model: Western Digital VelociRaptor 2.5″ SATA hard drive
- Rotational speed: 10,000 RPM
- Average latency: 3 ms (0.003 seconds)
- Average seek time: 4.2 (r)/4.7 (w) = 4.45 ms (0.0045 seconds)
- Calculated IOPS for this disk: 1/(0.003 + 0.0045) = about 133 IOPS
As you can see, the values for each kind of drive don’t radically change from source to source.
Sources:
- http://blog.aarondelp.com/2009/10/its-now-all-about-iops.html
- http://www.yellow-bricks.com/2009/12/23/iops/
- http://www.tomshardware.com/forum/251893-32-raid-raid
