磁盘性能--IOPS和吞吐量

梦里梦外; 2022-04-10 08:55 311阅读 0赞

## 一. Wikepedia上有关IOPS 的说明 ##

链接如下：[http://en.wikipedia.org/wiki/IOPS][http_en.wikipedia.org_wiki_IOPS]

IOPS ([Input/Output][Input_Output] OperationsPer Second, pronounced i-ops) is a common performance measurement used to [benchmark][] [computer storage][] devices like [harddisk drives][] (HDD), [solid state drives][] (SSD), and [storage area networks][] (SAN). As with anybenchmark, IOPS numbers published by storage device manufacturers do notguarantee real-world application performance.

IOPS can bemeasured with applications such as [Iometer][] (originallydeveloped by [Intel][]),as well as [IOzone][] and [FIO][][\[3\]][3] and isprimarily used with [servers][] to find the best storageconfiguration.

The specificnumber of IOPS possible in any system configuration will vary greatly dependingupon the variables the tester enters into the program, including the balance ofread and write operations, the mix of [sequential][] and [random][] accesspatterns, the number of worker [threads][] and queue depth, as well asthe data block sizes.[\[1\]][1] Thereare other factors which can also affect the IOPS results including the systemsetup, storage drivers, OS background operations, etc. Also, when testing SSDsin particular, there are preconditioning considerations that must be taken intoaccount.[\[4\]][4]

### 1.1 Performance characteristics ###

The most commonperformance characteristics measured are sequential and random operations.

Random access compared tosequential access:

![0_1319635254YmYP.gif][]

Sequential operations access locations on the storage device in a [contiguous manner][] and are generally associated withlarge data transfer sizes, e.g., 128 [KB][].

Random operations access locations on the storage device in a non-contiguous mannerand are generally associated with small data transfer sizes, e.g., 4 KB.

The most commonperformance characteristics are as follows:

<table> 
 <tbody> 
 <tr> 
 <td> Measurement </td> 
 <td> Description </td> 
 </tr> 
 <tr> 
 <td> Total IOPS </td> 
 <td> Total number of I/O operations per second (when performing a mix of read and write tests) </td> 
 </tr> 
 <tr> 
 <td> Random Read IOPS </td> 
 <td> Average number of random read I/O operations per second </td> 
 </tr> 
 <tr> 
 <td> Random Write IOPS </td> 
 <td> Average number of random write I/O operations per second </td> 
 </tr> 
 <tr> 
 <td> Sequential Read IOPS </td> 
 <td> Average number of sequential read I/O operations per second </td> 
 </tr> 
 <tr> 
 <td> Sequential Write IOPS </td> 
 <td> Average number of sequential write I/O operations per second </td> 
 </tr> 
 </tbody> 
</table>

For HDDs and similar electromechanical storage devices, the random IOPS numbers are primarily dependent upon the storagedevice's random [seek time][], whereas for SSDs and similar solid statestorage devices, the random IOPS numbers are primarily dependent upon thestorage device's internal controller and memory interface speeds.

On both types ofstorage devices the sequential IOPS numbers (especially when using a largeblock size) typically indicate the maximum sustained bandwidth that the storagedevice can handle.[\[1\]][1]

Often sequential IOPS arereported as a simple [MB/s][MB_s] number asfollows:

IOPS \* TransferSizeInBytes = BytesPerSec (withthe answer typically converted to [MegabytesPerSec][])

Some HDDs willimprove in performance as the number of outstanding IO's (i.e. queue depth)increases. This is usually the result of more advanced controller logic on thedrive performing command queuing and reordering commonly called either [Tagged Command Queuing][] (TCQ) or [Native Command Queuing][] (NCQ).

Mostcommodity [SATA][] driveseither cannot do this, or their implementation is so poor that no performancebenefit can be seen. Enterprise class SATA drives, such as the [Western Digital Raptor][] and SeagateBarracuda NL will improve by nearly 100% with deep queues.[\[5\]][5] High-end [SCSI][] drives morecommonly found in servers, generally show much greater improvement, withthe [Seagate][] Savvio exceeding 400 IOPS—more thandoubling its performance.\[[citation needed][]\]

While traditional HDDs have about the same IOPS for read and write operations,most [NAND flash-based][] SSDs are much slower writingthan reading due to the inability to rewrite directly into a previously writtenlocation forcing a procedure called [garbage collection][].[\[6\]][6][\[7\]][7][\[8\]][8] This hascaused hardware test sites to start to do IOPS testing, providing independentlymeasured results.

Newerflash SSD drives such as the Intel X25-E have much higher IOPS than traditionalhard disk drives. In a test done by Xssist, using IOmeter, 4 KB randomtransfers, 70/30 read/write ratio, queue depth 4, the IOPS delivered by theIntel X25-E 64 GB G1 started around 10000 IOPs, and dropped sharply after8 minutes to 4000 IOPS, and continued to decrease gradually for the next 42minutes. IOPS vary between 3000 to 4000 from around the 50th minutes onwardsfor the rest of the 8+ hours test run.[\[9\]][9] Even with thedrop in random IOPS after the 50th minute, the X25-E still has much higher IOPScompared to traditional hard disk drives. Some SSDs, including the [OCZ][] RevoDrive 3 x2PCIe using the [SandForce][] controller, have shown much higher sustainedwrite performance that more closely matches the read speed.[\[10\]][10]

### 1.2 示例 ###

<table> 
 <tbody> 
 <tr> 
 <td> Device </td> 
 <td> Type </td> 
 <td> IOPS </td> 
 <td> Interface </td> 
 <td> Notes </td> 
 </tr> 
 <tr> 
 <td> 7,200&nbsp;<a title="Revolutions per minute" href="http://en.wikipedia.org/wiki/Revolutions_per_minute" rel="nofollow">rpm</a>&nbsp;<a title="SATA" href="http://en.wikipedia.org/wiki/SATA" rel="nofollow">SATA</a>&nbsp;drives </td> 
 <td> <a title="Hard disk drive" href="http://en.wikipedia.org/wiki/Hard_disk_drive" rel="nofollow">HDD</a> </td> 
 <td> ~75-100 IOPS<a href="http://en.wikipedia.org/wiki/IOPS#cite_note-Symantec-1" rel="nofollow">[2]</a> </td> 
 <td> SATA 3&nbsp;<a title="Data rate units" href="http://en.wikipedia.org/wiki/Data_rate_units#Gigabit_per_second" rel="nofollow">Gb/s</a> </td> 
 </tr> 
 <tr> 
 <td> 10,000 rpm SATA drives </td> 
 <td> HDD </td> 
 <td> ~125-150 IOPS<a href="http://en.wikipedia.org/wiki/IOPS#cite_note-Symantec-1" rel="nofollow">[2]</a> </td> 
 <td> SATA 3 Gb/s </td> 
 </tr> 
 <tr> 
 <td> 15,000 rpm&nbsp;<a title="Serial Attached SCSI" href="http://en.wikipedia.org/wiki/Serial_Attached_SCSI" rel="nofollow">SAS</a>&nbsp;drives </td> 
 <td> HDD </td> 
 <td> ~175-210 IOPS&nbsp;<a href="http://en.wikipedia.org/wiki/IOPS#cite_note-Symantec-1" rel="nofollow">[2]</a> </td> 
 <td> SAS </td> 
 </tr> 
 </tbody> 
</table>

## 二. IOPS 说明 ##

### 2.1 IOPS (Input/Output Per Second) ###

IOPS 即每秒的输入输出量(或读写次数)，是衡量磁盘性能的主要指标之一。IOPS是指单位时间内系统能处理的I/O请求数量，一般以每秒处理的I/O请求数量为单位，I/O请求通常为读或写数据操作请求。例如，主机写入一个最小的[数据块][Link 1]，也要经过“发送写入请求、写入数据、收到写入确认”等三个步骤，也就是3个存储端访问。

随机读写频繁的应用，如OLTP(OnlineTransaction Processing)，IOPS是关键衡量指标。

另一个重要指标是数据吞吐量(Throughput)，指单位时间内可以成功传输的数据数量。对于大量顺序读写的应用，如VOD(Video On Demand)，则更关注吞吐量指标。

传统磁盘本质上一种机械装置，如FC, SAS, SATA磁盘，转速通常为5400/7200/10K/15K rpm不等。影响磁盘的关键因素是磁盘服务时间，即磁盘完成一个I/O请求所花费的时间，它由寻道时间、旋转延迟和数据传输时间三部分构成。

（1）寻道时间

Tseek是指将读写磁头移动至正确的磁道上所需要的时间。寻道时间越短，I/O操作越快，目前磁盘的平均寻道时间一般在3－15ms。

（2）旋转延迟

Trotation是指盘片旋转将请求数据所在扇区移至读写磁头下方所需要的时间。旋转延迟取决于磁盘转速，通常使用磁盘旋转一周所需时间的1/2表示。比如，7200 rpm的磁盘平均旋转延迟大约为60\*1000/7200/2 = 4.17ms，而转速为15000 rpm的磁盘其平均旋转延迟约为2ms。

（3）数据传输时间

Ttransfer是指完成传输所请求的数据所需要的时间，它取决于数据传输率，其值等于数据大小除以数据传输率。目前IDE/ATA能达到133MB/s（MBPS），SATA II可达到300MB/s的接口数据传输率，数据传输时间通常远小于前两部分时间。

IOPS（每秒IO次数） = 1s/(寻道时间+旋转延迟+数据传输时间)

因此，理论上可以计算出磁盘的最大IOPS，即IOPS = 1000ms/ (Tseek + Troatation)，忽略数据传输时间。假设磁盘平均物理寻道时间为3ms, 磁盘转速为7200,10K,15Krpm，则磁盘IOPS理论最大值分别为:

IOPS = 1000 / (3 + 60000/7200/2)  = 140  
IOPS = 1000 / (3 + 60000/10000/2) = 167  
IOPS = 1000 / (3 + 60000/15000/2) = 200

下面列一下不同的硬盘所能支撑的流量大小：

10 K rpm 15 K rpm ATA

———      ———      ———

10M/s       13M/s       8M/s

每个物理硬盘能处理的IOPS是有限制的，如

10 K rpm 15 K rpm ATA

———      ———     ———

100          150           50

IOPS的主要取决与阵列的算法，cache命中率，以及磁盘个数。我们假定一个case，业务的iops是10000，读cache命中率是30%，读iops为60%，写iops为40%，磁盘个数为120，那么分别计算在raid5与raid10的情况下，每个磁盘的iops为多少。

raid5:

单块盘的iops = (10000\*(1-0.3)\*0.6 + 4 \* (10000\*0.4))/120 = (4200 + 16000)/120 = 168

这里的10000\*(1-0.3)\*0.6表示是读的iops，比例是0.6，除掉cache命中，实际只有4200个iops

而4 \* (10000\*0.4) 表示写的iops，因为每一个写，在raid5中，实际发生了4个io，所以写的iops为16000个

为了考虑raid5在写操作的时候，那2个读操作也可能发生命中，所以更精确的计算为：

单块盘的iops = (10000\*(1-0.3)\*0.6 + 2 \* (10000\*0.4)\*(1-0.3) + 2 \* (10000\*0.4))/120 = (4200 + 5600 + 8000)/120 = 148

计算出来单个盘的iops为148个，基本达到磁盘极限

raid10:  单块盘的iops = (10000\*(1-0.3)\*0.6 + 2 \* (10000\*0.4))/120  =   (4200 + 8000)/120   = 102

可以看到，因为raid10对于一个写操作，只发生2次io，所以，同样的压力，同样的磁盘，每个盘的iops只有102个，还远远低于磁盘的极限iops。

### 2.2 固态硬盘的IOPS ###

固态硬盘SSD是一种电子装置， 避免了传统磁盘在寻道和旋转上的时间花费，存储单元寻址开销大大降低，因此IOPS可以非常高，能够达到数万甚至数十万。实际测量中，IOPS数值会受到很多因素的影响，包括I/O负载特征(读写比例，顺序和随机，工作线程数，队列深度，数据记录大小)、系统配置、操作系统、磁盘驱动等等。因此对比测量磁盘IOPS时，必须在同样的测试基准下进行，即便如何也会产生一定的随机不确定性。

通常情况下，IOPS可细分为如下几个指标：

Toatal IOPS：混合读写和顺序随机I/O负载情况下的磁盘IOPS，这个与实际I/O情况最为相符，大多数应用关注此指标。

Random Read IOPS：100%随机读负载情况下的IOPS。

Random WriteIOPS：100%随机写负载情况下的IOPS。

Sequential ReadIOPS：100%顺序负载读情况下的IOPS。

Sequential WriteIOPS：100%顺序写负载情况下的IOPS。

## 三.ORION 工具说明 ##

ORION (OracleI/O Calibration Tool) Oracle 公司推出的一个校准数据库的存储系统 I/O 性能的独立工具。有关该工具的说明，参考：

[Oracle ORION IO 测试工具][Oracle ORION IO]

[http://blog.csdn.net/tianlesoftware/article/details/5965331][Oracle ORION IO]

我们使用ORION 工具测试一下看看：

\[root@qs-xe-dzora-pd software\]\# cat dave.lun

/dev/sdb1

\[root@qs-xe-dzora-pd software\]\#  ./orion\_linux\_x86-64 -run advanced -testname dave -num\_disks 2

ORION: ORacle IO Numbers -- Version11.1.0.7.0

dave\_20111026\_2026

Test will take approximately 16 minutes

Larger caches may take longer

查看生成的结果：

\[root@qs-xe-dzora-pd software\]\# ls dave\*

dave\_20111026\_2026\_iops.csv  dave\_20111026\_2026\_summary.txt  dave.lun\_20111026\_2025\_summary.txt

dave\_20111026\_2026\_lat.csv   dave\_20111026\_2026\_trace.txt

dave\_20111026\_2026\_mbps.csv  dave.lun

\[root@qs-xe-dzora-pd software\]\# cat dave\_20111026\_2026\_summary.txt

ORION VERSION 11.1.0.7.0

Commandline:

\-run advanced -testname dave -num\_disks 2

This maps to this test:

Test: dave

Small IO size: 8 KB

Large IO size: 1024 KB

IO Types: Small Random IOs, Large RandomIOs

Simulated Array Type: CONCAT

Write: 0%

Cache Size: Not Entered

Duration for each Data Point: 60 seconds

Small Columns:,      0

Large Columns:,      0,     1,      2,      3,     4

Total Data Points: 15

Name: /dev/sdb1 Size: 449495069184

1 FILEs found.

Maximum Large MBPS=159.61 @ Small=0 andLarge=4

Maximum Small IOPS=534 @ Small=10 andLarge=0

Minimum Small Latency=4.97 @ Small=1 andLarge=0

这里显示的吞吐量是160MBPS. IOPS 为534.

## 转自网络:[http://blog.csdn.net/tianlesoftware/article/details/6908603][http_blog.csdn.net_tianlesoftware_article_details_6908603] ##

[http_en.wikipedia.org_wiki_IOPS]: http://en.wikipedia.org/wiki/IOPS
[Input_Output]: http://en.wikipedia.org/wiki/Input/Output
[benchmark]: http://en.wikipedia.org/wiki/Benchmark_%28computing%29
[computer storage]: http://en.wikipedia.org/wiki/Data_storage_device
[harddisk drives]: http://en.wikipedia.org/wiki/Hard_disk_drive
[solid state drives]: http://en.wikipedia.org/wiki/Solid_state_drives
[storage area networks]: http://en.wikipedia.org/wiki/Storage_area_network
[Iometer]: http://en.wikipedia.org/wiki/Iometer
[Intel]: http://en.wikipedia.org/wiki/Intel
[IOzone]: http://en.wikipedia.org/wiki/IOzone
[FIO]: http://en.wikipedia.org/wiki/FIO_%28software%29
[3]: http://en.wikipedia.org/wiki/IOPS#cite_note-2
[servers]: http://en.wikipedia.org/wiki/Server_%28computing%29
[sequential]: http://en.wikipedia.org/wiki/Sequential_access
[random]: http://en.wikipedia.org/wiki/Random_access
[threads]: http://en.wikipedia.org/wiki/Thread_%28computer_science%29
[1]: http://en.wikipedia.org/wiki/IOPS#cite_note-Scott_Lowe-0
[4]: http://en.wikipedia.org/wiki/IOPS#cite_note-Kent_Smith-3
[0_1319635254YmYP.gif]: /images/20220401/a93bff5ddb774b94a79188550facee03.png
[contiguous manner]: http://en.wikipedia.org/wiki/Contiguity#Computer_science
[KB]: http://en.wikipedia.org/wiki/Kilobyte
[seek time]: http://en.wikipedia.org/wiki/Seek_time
[MB_s]: http://en.wikipedia.org/wiki/MB/s#Megabyte_per_second
[MegabytesPerSec]: http://en.wikipedia.org/wiki/Megabytes_per_second
[Tagged Command Queuing]: http://en.wikipedia.org/wiki/Tagged_Command_Queuing
[Native Command Queuing]: http://en.wikipedia.org/wiki/Native_Command_Queuing
[SATA]: http://en.wikipedia.org/wiki/SATA
[Western Digital Raptor]: http://en.wikipedia.org/wiki/Western_Digital_Raptor
[5]: http://en.wikipedia.org/wiki/IOPS#cite_note-4
[SCSI]: http://en.wikipedia.org/wiki/SCSI
[Seagate]: http://en.wikipedia.org/wiki/Seagate_Technology
[citation needed]: http://en.wikipedia.org/wiki/Wikipedia:Citation_needed
[NAND flash-based]: http://en.wikipedia.org/wiki/Flash_memory
[garbage collection]: http://en.wikipedia.org/wiki/Garbage_collection_%28SSD%29
[6]: http://en.wikipedia.org/wiki/IOPS#cite_note-IBM_WA-5
[7]: http://en.wikipedia.org/wiki/IOPS#cite_note-OCZ_WA-6
[8]: http://en.wikipedia.org/wiki/IOPS#cite_note-7
[9]: http://en.wikipedia.org/wiki/IOPS#cite_note-8
[OCZ]: http://en.wikipedia.org/wiki/OCZ
[SandForce]: http://en.wikipedia.org/wiki/SandForce
[10]: http://en.wikipedia.org/wiki/IOPS#cite_note-9
[Link 1]: http://baike.baidu.com/view/702806.htm
[Oracle ORION IO]: http://blog.csdn.net/tianlesoftware/article/details/5965331
[http_blog.csdn.net_tianlesoftware_article_details_6908603]: http://blog.csdn.net/tianlesoftware/article/details/6908603