huawei tecal es3000 high performance pcie ssd card ... ss… · huawei tecal es3000 high...

HUAWEI Tecal ES3000 High Performance PCIe SSD Card

Performance Test Guide

Issue 01

Date 2013-03-18

HUAWEI TECHNOLOGIES CO., LTD.

Issue 01 (2013-03-18) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd..

ii

Copyright © Huawei Technologies Co., Ltd. 2013. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior

written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective

holders.

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and

the customer. All or part of the products, services and features described in this document may not be

within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,

information, and recommendations in this document are provided "AS IS" without warranties, guarantees or

representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the

preparation of this document to ensure accuracy of the contents, but all statements, information, and

recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://enterprise.huawei.com


Performance Test Guide About This Document



iii

About This Document

Purpose This document describes the environment and methods for testing the HUAWEI Tecal

ES3000 high-performance PCIe SSD card on various operating systems (OSs).

Intended Audience

This document is intended for:

Technical support engineers

R&D engineers

Marketing and sales personnel

Maintenance engineers

Users

Change History

Changes between document issues are cumulative. The latest document issue contains all the

changes made in earlier issues.

Issue 01 (2013-03-18)

This issue is the first official release.


Performance Test Guide Contents



iv

Contents

About This Document ................................................................................................................... iii

1 Overview ......................................................................................................................................... 5

2 Software and Hardware ............................................................................................................... 6

2.1 Hardware Information ....................................................................................................................................... 6

2.2 Software and Logic Version .............................................................................................................................. 6

2.3 Test Tool ............................................................................................................................................................ 6

3 Performance Test on Linux ......................................................................................................... 7

3.1 Test Environment ............................................................................................................................................... 7

3.2 Performance Test ............................................................................................................................................... 8

3.2.1 Testing the Sequential Write Bandwidth at 1 MB Data Block ................................................................ 8

3.2.2 Testing the Sequential Read Bandwidth at 1 MB Data Block ................................................................. 9

3.2.3 Testing the Random Write IOPS at 4 KB Data Block ........................................................................... 10

3.2.4 Testing the Random Read IOPS at 4 KB Data Block............................................................................ 12

3.2.5 Testing the Random Write Latency at 4 KB Data Block ....................................................................... 13

3.2.6 Testing the Random Read Latency at 4 KB Data Block ....................................................................... 15

3.2.7 Testing the Mixed Read/Write IOPS (7:3) at 4 KB Data Block ............................................................ 16

4 Performance Test on Windows................................................................................................. 19

4.1 Test Environment ............................................................................................................................................. 19

4.2 Performance Test ............................................................................................................................................. 21

4.2.1 Testing the Sequential Write Bandwidth at 1 MB Data Block .............................................................. 21

4.2.2 Testing the Sequential Read Bandwidth at 1 MB Data Block ............................................................... 23

4.2.3 Testing the Random Write IOPS at 4 KB Data Block ........................................................................... 24

4.2.4 Testing the Random Read IOPS at 4 KB Data Block............................................................................ 27

4.2.5 Testing the Random Write Latency at 4 KB Data Block ....................................................................... 29

4.2.6 Testing the Random Read Latency at 4 KB Data Block ....................................................................... 30

4.2.7 Testing the Mixed Read/Write IOPS (7:3) at 4 KB Data Block ............................................................ 32

5 Performance Test on the VMware OS..................................................................................... 34

5.1 Test Environment ............................................................................................................................................. 34

5.2 Performance Test ............................................................................................................................................. 46


Performance Test Guide 1 Overview



5

1 Overview

This document describes the environment and methods for testing the HUAWEI Tecal

ES3000 high-performance PCIe SSD card (ES3000 for short) on various OSs.

The ES3000 can be installed in servers such as the HUAWEI Tecal RH2285 V2, HUAWEI

Tecal RH2288 V2, HUAWEI Tecal RH5885, IBM X3850, Dell R720, and HP G380. This

document uses the RH2285 V2 for an example.

This document provides reference for R&D engineers and marketing personnel.


Performance Test Guide 2 Software and Hardware



6

2 Software and Hardware

2.1 Hardware Information

Server: Huawei Tecal RH2285 V2

CPU: Intel®

Xeon® CPU E5-2603 at 1.80 GHz

Processor quantity: 8

Memory: 32 GB DIMM

PCIe card: ES3000

2.2 Software and Logic Version

Driver Version: 2.0.0.20

HIO 2 Size: 1204 GB

HIO 2 Bridge FW VER: 228

HIO 2 Controller FW VER: 228

HIO 2 PCB VER: .B

HIO 2 Upper PCB VER: .B

2.3 Test Tool

Test tool: fio 2.08

Obtain the test tool from the following websites:

Linux: http://freecode.com/projects/fio

Windows: http://www.bluestop.org/fio/

http://freecode.com/projects/fio

http://www.bluestop.org/fio/


Performance Test Guide 3 Performance Test on Linux



7

3 Performance Test on Linux

3.1 Test Environment

Procedure

1. Install an ES3000 to a PCIe 2.0 x8 slot in an RH2285 V2.

The ES3000 is not hot-swappable. Power off the server before the installation.

2. Power on the server and install the SLES11, RHEL 5.x, RHEL 6.x, or CentOS 6.x OS.

3. Run lspci | grep Mass to check whether the ES3000 is normal after OS installation.

The command output similar to the following is displayed:

If the ES3000 is displayed after Mass storage controller, the ES3000 is properly installed. If

not, power off the server and check whether the SSD card is properly installed.

4. Upload the ES3000 driver to the server over File Transfer Protocol (FTP), go to the

directory where the driver package is stored, and run rpm –ivh

hio-2.0.0.20-2.6.32_71.el6.x86_64.rpm to install the driver.

5. Run hio_info to check the driver installation.

If the driver is successfully installed, the information similar to the following is displayed:

If driver installation fails, run dmesg | grep hio to check error information.

NOTE





8

6. Download the fio software from the website provided in 2.3 Test Tool" and install the fio

test tool.

An executable file is generated after fio is installed.

The test environment establishment is complete. You can start the performance test.

3.2 Performance Test

3.2.1 Testing the Sequential Write Bandwidth at 1 MB Data Block

Procedure

1. Run hio_cleardata -d /dev/hioa and enter yes to clear data stored on the ES3000.


2. Run ./fio --name=ssd --numjobs=1 --filename=/dev/hioa --bs=1m --iodepth=256

--rw=write --ioengine=libaio --direct=1 --sync=0 --norandommap --group_reporting

--runtime=3600 --time_based in the directory where the executable file of fio is stored.

filename specifies the device to be tested, runtime specifies the operating time (the unit is second), and

bs specifies the data block size.

The test is complete after an hour. The test results similar to the following are displayed:

NOTE





9

3.2.2 Testing the Sequential Read Bandwidth at 1 MB Data Block

Procedure

1. Run ./fio --name=ssd --numjobs=1 --filename=/dev/hioa --bs=1m --iodepth=256

--rw=read --ioengine=libaio --direct=1 --sync=0 --norandommap

--group_reporting --runtime=3600 --time_based in the directory where the

executable file of fio is stored.




NOTE

linux:/home/fio # ./fio --name=ssd --numjobs=1 --filename=/dev/hioa --bs=1m

--iodepth=256 --rw=write --ioengine=libaio --direct=1 --sync=0 --norandommap

--group_reporting --runtime=3600 --time_based

ssd: (g=0): rw=write, bs=1M-1M/1M-1M, ioengine=libaio, iodepth=256

fio 1.58

Starting 1 process

ssd: (groupid=0, jobs=1): err= 0: pid=3274

write: io=4252.5GB, bw=1209.6MB/s, iops=1209 , runt=3600207msec

slat (usec): min=25 , max=322788 , avg=80.66, stdev=334.01

clat (msec): min=18 , max=420 , avg=211.55, stdev=16.84

lat (msec): min=18 , max=420 , avg=211.63, stdev=16.84

bw (KB/s) : min= 0, max=1787904, per=93.48%, avg=1157751.11,

stdev=314428.12

cpu : usr=0.21%, sys=9.79%, ctx=4353497, majf=0, minf=24

IO depths : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0%

submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%

complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.1%

issued r/w/d: total=0/4354518/0, short=0/0/0

lat (msec): 20=0.01%, 50=0.02%, 100=0.02%, 250=98.08%, 500=1.88%

Run status group 0 (all jobs):

WRITE: io=4252.5GB, aggrb=1209.6MB/s, minb=1238.6MB/s, maxb=1238.6MB/s,

mint=3600207msec, maxt=3600207msec

Disk stats (read/write):

hioa: ios=499/34834408, merge=0/0, ticks=10267/921193892, in_queue=921291694,

util=100.00%





10

3.2.3 Testing the Random Write IOPS at 4 KB Data Block

Procedure



linux:/home/fio # ./fio --name=ssd --numjobs=1 --filename=/dev/hioa --bs=1m

--iodepth=256 --rw=read --ioengine=libaio --direct=1 --sync=0 --norandommap


ssd: (g=0): rw=read, bs=1M-1M/1M-1M, ioengine=libaio, iodepth=128

...

ssd: (g=0): rw=read, bs=1M-1M/1M-1M, ioengine=libaio, iodepth=128

fio 1.58

Starting 16 processes


read : io=3921.9GB, bw=2229.1MB/s, iops=2229 , runt=1800917msec


clat (msec): min=38 , max=1835 , avg=918.29, stdev=17.21



stdev=49662.31


IO depths : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%,

32=0.1%, >=64=100.0%

submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%,

64=0.0%, >=64=0.0%

complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%,

64=0.0%, >=64=0.1%


lat (msec): 50=0.01%, 100=0.01%, 250=0.01%, 500=0.02%, 750=0.02%

lat (msec): 1000=99.91%, 2000=0.05%


READ: io=3921.9GB, aggrb=2229.1MB/s, minb=2283.5MB/s,

maxb=2283.5MB/s, mint=1800917msec, maxt=1800917msec



util=100.00%





11

2. Run ./fio --name=ssd --numjobs=4 --filename=/dev/hioa --bs=4k --iodepth=64

--rw=randwrite --ioengine=libaio --direct=1 --sync=0 --norandommap






NOTE





12

3.2.4 Testing the Random Read IOPS at 4 KB Data Block

Procedure


--rw=randread --ioengine=libaio --direct=1 --sync=0 --norandommap





NOTE

linux:/home/fio # ./fio --name=ssd --numjobs=4 --filename=/dev/hioa --bs=4k

--iodepth=64 --rw=randwrite --ioengine=libaio --direct=1 --sync=0 --norandommap


ssd: (g=0): rw=randwrite, bs=4K-4K/4K-4K, ioengine=libaio, iodepth=64

...


fio 1.58



write: io=3360.8GB, bw=489445KB/s, iops=122361 , runt=7200011msec

slat (usec): min=1 , max=1412 , avg= 3.35, stdev= 1.11

clat (usec): min=509 , max=32671 , avg=8364.45, stdev=2873.79

lat (usec): min=515 , max=32674 , avg=8367.93, stdev=2873.80

bw (KB/s) : min=29856, max=164670, per=12.51%, avg=61224.31, stdev=17485.13


IO depths : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0%

submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%

complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%,

64=0.0%, >=64=0.1%


lat (usec): 750=0.01%

lat (msec): 2=0.01%, 4=8.91%, 10=63.11%, 20=27.90%, 50=0.07%


WRITE: io=3360.8GB, aggrb=489444KB/s, minb=501191KB/s, maxb=501191KB/s,




util=100.00%





13


3.2.5 Testing the Random Write Latency at 4 KB Data Block

Procedure


linux:/home/fio # ./fio --name=ssd --numjobs=4 --filename=/dev/hioa --bs=4k --iodepth=64 --rw=randread --ioengine=libaio --direct=1 --sync=0 --norandommap --group_reporting --runtime=3600 --time_based

ssd: (g=0): rw=randread, bs=4K-4K/4K-4K, ioengine=libaio, iodepth=64

...


fio 1.58



read : io=3891.9GB, bw=2214.1MB/s, iops=566786 , runt=1800005msec






IO depths : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0%

submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%

complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.1%


lat (usec): 2=0.01%, 10=0.01%, 20=0.01%, 50=0.01%, 100=0.02%

lat (usec): 250=5.82%, 500=2.52%, 750=0.70%, 1000=0.30%

lat (msec): 2=0.31%, 4=54.19%, 10=36.12%, 20=0.01%


READ: io=3891.9GB, aggrb=2214.1MB/s, minb=2267.2MB/s, maxb=2267.2MB/s, mint=1800005msec, maxt=1800005msec


hioa: ios=1020081690/0, merge=0/0, ticks=323331754/0, in_queue=326416395, util=100.00%





14



--rw=randwrite --ioengine=libaio --direct=1 --sync=0 --norandommap






NOTE





15

3.2.6 Testing the Random Read Latency at 4 KB Data Block

Procedure


--rw=randread --ioengine=libaio --direct=1 --sync=0 --norandommap





NOTE

linux:/home/fio # ./fio --name=ssd --numjobs=1 --filename=/dev/hioa --bs=4k --iodepth=1 --rw=randwrite --ioengine=libaio --direct=1 --sync=0 --norandommap --group_reporting --runtime=1800 --time_based


fio 1.58

Starting 1 process


write: io=397997MB, bw=226416KB/s, iops=56604 , runt=1800000msec


clat (usec): min=0 , max=371 , avg=11.70, stdev= 0.69

lat (usec): min=8 , max=375 , avg=16.30, stdev= 0.70



IO depths : 1=100.0%, 2=0.0%, 4=0.0%, 8=0.0%, 16=0.0%, 32=0.0%, >=64=0.0%

submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%

complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%


lat (usec): 2=0.01%, 4=0.01%, 10=0.06%, 20=99.92%, 50=0.02%

lat (usec): 100=0.01%, 250=0.01%, 500=0.01%


WRITE: io=397997MB, aggrb=226416KB/s, minb=231850KB/s, maxb=231850KB/s, mint=1800000msec, maxt=1800000msec







16


3.2.7 Testing the Mixed Read/Write IOPS (7:3) at 4 KB Data Block

Procedure



linux:/home/fio # ./fio --name=ssd --numjobs=1 --filename=/dev/hioa --bs=4k --iodepth=1 --rw=randread --ioengine=libaio --direct=1 --sync=0 --norandommap --group_reporting --runtime=1800 --time_based


fio 1.58

Starting 1 process


read : io=69374MB, bw=39466KB/s, iops=9866 , runt=1800001msec






IO depths : 1=100.0%, 2=0.0%, 4=0.0%, 8=0.0%, 16=0.0%, 32=0.0%, >=64=0.0%

submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%

complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%


lat (usec): 50=6.99%, 100=48.41%, 250=44.42%, 500=0.18%, 750=0.01%

lat (usec): 1000=0.01%

lat (msec): 2=0.01%, 4=0.01%, 10=0.01%


READ: io=69374MB, aggrb=39466KB/s, minb=40413KB/s, maxb=40413KB/s, mint=1800001msec, maxt=1800001msec







17


--rw=randrw --rwmixwrite=30 --ioengine=libaio --direct=1 --sync=0

--norandommap --group_reporting --runtime=3600 --time_based in the directory

where the executable file of fio is stored.




NOTE





18

linux:/home/fio # ./fio --name=ssd --numjobs=4 --filename=/dev/hioa --bs=4k

--iodepth=64 --rw=randrw --rwmixwrite=30 --ioengine=libaio --direct=1 --sync=0

--norandommap --group_reporting --runtime=1800 --time_based

ssd: (g=0): rw=randrw, bs=4K-4K/4K-4K, ioengine=libaio, iodepth=64

...

ssd: (g=0): rw=randrw, bs=4K-4K/4K-4K, ioengine=libaio, iodepth=64

fio 1.58


Jobs: 4 (f=4): [mmmm] [100.0% done] [717.7M/307.4M /s] [179K/76.9K iops] [eta

00m:00s]


read : io=1334.6GB, bw=777449KB/s, iops=194362 , runt=1800004msec




bw (KB/s) : min=142304, max=348600, per=25.00%, avg=194393.22,

stdev=18100.35

write: io=585725MB, bw=333211KB/s, iops=83302 , runt=1800004msec





stdev=7669.32


IO depths : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%,

32=0.1%, >=64=100.0%

submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%,

64=0.0%, >=64=0.0%

complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%,

64=0.1%, >=64=0.0%


lat (usec): 2=0.01%, 4=0.01%, 10=0.01%, 20=0.41%, 50=10.90%

lat (usec): 100=6.35%, 250=17.03%, 500=14.63%, 750=9.05%, 1000=7.16%

lat (msec): 2=20.17%, 4=12.74%, 10=1.54%, 20=0.01%


READ: io=1334.6GB, aggrb=777449KB/s, minb=796108KB/s,

maxb=796108KB/s, mint=1800004msec, maxt=1800004msec

WRITE: io=585725MB, aggrb=333211KB/s, minb=341208KB/s,

maxb=341208KB/s, mint=1800004msec, maxt=1800004msec


hioa: ios=349823322/149932587, merge=0/0, ticks=383552202/32236630,

in_queue=426810332, util=100.00%


Performance Test Guide 4 Performance Test on Windows



19

4 Performance Test on Windows


Procedure

1. Install an ES3000 to a PCIe 2.0 x8 slot in an RH2285 V2. The ES3000 is not

hot-swappable. Power off the server before the installation.

2. Power on the server and install the Windows 2008 Server R2 64-bit OS.

3. Check whether the ES3000 is detected in Server Manager after OS installation.

Figure 4-1 Server Manager

If Huawei SSD Device is displayed in Server Manager, the ES3000 is properly installed. If

not, power off the server and check the SSD card installation.

4. Copy the ES3000 driver to the desktop and double-click

HW_SSD_Driver_v2.0.0.20_3.exe to install the driver.





20

5. Double-click Huawei SSD Utility 2.0.0.20 after the driver is installed. In the displayed

window, click , as shown in Figure 4-2.

Figure 4-2 Huawei SSD Utility 2.0.0.20

If information similar to that in Figure 4-3 is displayed, the driver is successfully installed.

The ES3000 is displayed in Server Manager, as shown in Figure 4-3.ES3000 detected in Server

Manager

6. Download the fio software from the website provided in 2.3 "Test Tool" and install the

fio test tool.

An executable file is generated after the fio installation.





21



4.2.1 Testing the Sequential Write Bandwidth at 1 MB Data Block

Procedure

1. Go to the directory where the HW SSD Utility is stored, run HioClearData -d 0 and

enter yes to clear data on the ES3000, as shown in Figure 4-4.

Figure 4-4 Clearing data on the ES3000

2. Run .\fio.exe --name=ssd --numjobs=1 --filename=\\.\PhysicalDrive1 --bs=1m

--iodepth=256 --rw=write --ioengine=windowsaio --direct=1 --sync=0






NOTE





22

Windows PowerShell

Copyright (C) 2009 Microsoft Corporation. All rights reserved.

PS C:\Users\Administrator\Desktop>.\fio.exe --name=ssd --numjobs=1

--filename=\\.\PhysicalDrive1 --bs=1m --iodepth=256 --rw=write --ioengine=windowsaio

--direct=1 --sync=0 --norandommap --group_reporting --runtime=3600 --time_based

ssd: (g=0): rw=write, bs=1M-1M/1M-1M, ioengine=windowsaio, iodepth=256

fio-2.0.8

Starting 1 thread


write: io=2097.0MB, bw=1223.6MB/s, iops=1223 , runt=3600137msec


clat (usec): min=980 , max=1015.6K, avg=139912.45, stdev=16933.54


clat percentiles (msec):

| 1.00th=[ 133], 5.00th=[ 135], 10.00th=[ 135], 20.00th=[ 137],

| 30.00th=[ 137], 40.00th=[ 137], 50.00th=[ 139], 60.00th=[ 139],

| 70.00th=[ 139], 80.00th=[ 141], 90.00th=[ 143], 95.00th=[ 143],

| 99.00th=[ 251], 99.50th=[ 260], 99.90th=[ 330], 99.95th=[ 338],

| 99.99th=[ 343]

bw (MB/s) : min= 1105, max= 1271, per=100.00%, avg=1222.91, stdev=130.99

lat (usec) : 1000=0.01%

lat (msec) : 2=0.01%, 4=0.01%, 10=0.01%, 20=0.01%, 50=0.02%

lat (msec) : 100=0.03%, 250=98.91%, 500=1.04%, 750=0.01%, 1000=0.01%

lat (msec) : 2000=0.01%


IO depths : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0%

submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%,

64=0.0%, >=64=0.0%

complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.1%

issued : total=r=0/w=6564889/d=0, short=r=0/w=0/d=0


WRITE: io=2097.3GB, aggrb=1223.6MB/s, minb=1123.6MB/s, maxb=1270.6MB/s, mint=3600137msec, maxt=3600137msec





23

4.2.2 Testing the Sequential Read Bandwidth at 1 MB Data Block

Procedure

1. Run .\fio.exe --name=ssd --numjobs=1 --filename=\\.\PhysicalDrive1 --bs=1m

--iodepth=256 --rw=read --ioengine=windowsaio --direct=1 --sync=0






NOTE





24

4.2.3 Testing the Random Write IOPS at 4 KB Data Block

Procedure

1. Run HioClearData -d 0 and enter yes to clear data stored on the ES3000.

Windows PowerShell



--filename=\\.\PhysicalDrive1 --bs=1m --iodepth=256 --rw=read --ioengine=windowsaio


ssd: (g=0): rw=read, bs=1M-1M/1M-1M, ioengine=windowsaio, iodepth=256

fio-2.0.8

Starting 1 thread


read : io=2672.0MB, bw=2279.7MB/s, iops=2279 , runt=3600105msec



lat (msec): min=1 , max=217 , avg=112.29, stdev= 2.00

clat percentiles (msec):

| 1.00th=[ 109], 5.00th=[ 111], 10.00th=[ 112], 20.00th=[ 112],

| 30.00th=[ 112], 40.00th=[ 113], 50.00th=[ 113], 60.00th=[ 114],

| 70.00th=[ 114], 80.00th=[ 114], 90.00th=[ 115], 95.00th=[ 115],

| 99.00th=[ 116], 99.50th=[ 116], 99.90th=[ 116], 99.95th=[ 117],

| 99.99th=[ 172]

bw (MB/s) : min= 1875, max= 2549, per=100.00%, avg=2335.61, stdev=23.42

lat (usec) : 750=0.01%, 1000=0.01%

lat (msec) : 2=0.01%, 4=0.01%, 10=0.01%, 20=0.01%, 50=0.01%

lat (msec) : 100=0.03%, 250=99.95%


IO depths : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0%

submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%

complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.1%



READ: io=3918.7GB, aggrb=2279.7MB/s, minb=2279.7MB/s, maxb=2279.7MB/s,






25

Figure 4-5 shows the HioClearData -d 0 command output.

Figure 4-5 HioClearData -d 0 command output

2. Run .\fio.exe --name=ssd --numjobs=4 --filename=\\.\PhysicalDrive1 --bs=4k

--iodepth=64 --rw=randwrite --ioengine=windowsaio --direct=1 --sync=0






NOTE





26

Windows PowerShell



--filename=/dev/hioa --bs=4k --iodepth=64 --rw=randwrite --ioengine=windowsaio


ssd: (g=0): rw=randwrite, bs=4K-4K/4K-4K, ioengine=windowsaio, iodepth=64

...


fio-2.0.8

Starting 4 threads


write: io=1773.1MB, bw=492508KB/s, iops=123127 , runt=3600001msec

slat (usec): min=0 , max=1000.2K, avg=14.70, stdev=1949.92

clat (usec): min=0 , max=541879K, avg=1650.28, stdev=291494.64

lat (usec): min=0 , max=541879K, avg=1664.96, stdev=291501.08

clat percentiles (usec):

| 1.00th=[ 0], 5.00th=[ 0], 10.00th=[ 0], 20.00th=[ 0],

| 30.00th=[ 44], 40.00th=[ 54], 50.00th=[ 63], 60.00th=[ 82],

| 70.00th=[ 103], 80.00th=[ 129], 90.00th=[ 197], 95.00th=[ 374],

| 99.00th=[ 3856], 99.50th=[ 5664], 99.90th=[15296], 99.95th=[82432],

| 99.99th=[1044480]


stdev=117602.02

lat (usec) : 2=28.45%, 4=0.01%, 10=0.01%, 20=0.01%, 50=5.30%

lat (usec) : 100=33.89%, 250=24.98%, 500=3.10%, 750=0.63%, 1000=0.35%

lat (msec) : 2=1.01%, 4=1.32%, 10=0.78%, 20=0.09%, 50=0.02%

lat (msec) : 100=0.01%, 250=0.02%, 500=0.01%, 750=0.01%, 1000=0.01%

lat (msec) : 2000=0.01%, >=2000=0.01%


IO depths : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%,

32=0.1%, >=64=100.0%

submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%,

64=0.0%, >=64=0.0%

complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%,

64=0.1%, >=64=0.0%









27

4.2.4 Testing the Random Read IOPS at 4 KB Data Block

Procedure


--iodepth=64 --rw=randread --ioengine=windowsaio --direct=1 --sync=0






NOTE





28

Windows PowerShell



--filename=\\.\PhysicalDrive1 --bs=4k --iodepth=64 --rw=randread --ioengine=libaio


ssd: (g=0): rw=randread, bs=4K-4K/4K-4K, ioengine=windowsaio, iodepth=64

...


fio-2.0.8

Starting 4 threads


read : io=8082GB, bw=2245.8MB/s, iops=561474 , runt=3600001msec


clat (usec): min=0 , max=425557K, avg=1564.55, stdev=243379.39

lat (usec): min=0 , max=425557K, avg=1578.46, stdev=243387.09


| 1.00th=[ 0], 5.00th=[ 0], 10.00th=[ 0], 20.00th=[ 0],

| 30.00th=[ 0], 40.00th=[ 147], 50.00th=[ 157], 60.00th=[ 167],

| 70.00th=[ 189], 80.00th=[ 217], 90.00th=[ 310], 95.00th=[ 442],

| 99.00th=[ 1464], 99.50th=[ 2800], 99.90th=[16768], 99.95th=[47360],

| 99.99th=[1187840]

bw (MB/s) : min= 2189, max=2258, per=29.61%, avg=2245.8,

stdev=127233.86

lat (usec) : 2=30.61%, 4=0.01%, 10=0.01%, 20=0.01%, 50=0.01%

lat (usec) : 100=0.25%, 250=54.13%, 500=10.99%, 750=1.76%, 1000=0.69%

lat (msec) : 2=0.86%, 4=0.36%, 10=0.20%, 20=0.06%, 50=0.04%

lat (msec) : 100=0.01%, 250=0.01%, 500=0.01%, 750=0.01%, 1000=0.01%

lat (msec) : 2000=0.01%, >=2000=0.01%


IO depths : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0%

submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%,

64=0.0%, >=64=0.0%

complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%,

64=0.1%, >=64=0.0%



READ: io=8082GB, aggrb=2246KB/s, minb=2189MB/s, maxb=2258KB/s,






29

4.2.5 Testing the Random Write Latency at 4 KB Data Block

Procedure



Figure 4-6 HioClearData -d 0 command output


--iodepth=1 --rw=randwrite --ioengine=windowsaio --direct=1 --sync=0






NOTE





30

4.2.6 Testing the Random Read Latency at 4 KB Data Block

Procedure


--iodepth=1 --rw=randread --ioengine=windowsaio --direct=1 --sync=0

Windows PowerShell



--filename=\\.\PhysicalDrive --bs=4k --iodepth=1 --rw=randwrite --ioengine=libaio



fio-2.0.8

Starting 1 thread


write: io=829404KB, bw=29357KB/s, iops=7339 , runt=3600001msec

slat (usec): min=0 , max=2190 , avg=14.02, stdev= 7.64




| 1.00th=[ 52], 5.00th=[ 61], 10.00th=[ 95], 20.00th=[ 107],

| 30.00th=[ 111], 40.00th=[ 117], 50.00th=[ 123], 60.00th=[ 126],

| 70.00th=[ 129], 80.00th=[ 131], 90.00th=[ 135], 95.00th=[ 143],

| 99.00th=[ 155], 99.50th=[ 159], 99.90th=[ 181], 99.95th=[ 193],

| 99.99th=[ 278]


lat (usec) : 2=0.01%, 4=0.01%, 10=0.01%, 20=0.01%, 50=0.05%

lat (usec) : 100=12.50%, 250=87.43%, 500=0.01%, 750=0.01%, 1000=0.01%

lat (msec) : 2=0.01%, 4=0.01%, 10=0.01%, 20=0.01%


IO depths : 1=100.0%, 2=0.0%, 4=0.0%, 8=0.0%, 16=0.0%, 32=0.0%, >=64=0.0%

submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%

complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%



WRITE: io=103210MB, aggrb=29357KB/s, minb=29357KB/s, maxb=29357KB/s,






31






NOTE

Windows PowerShell



--filename=\\.\PhysicalDrive1 --bs=4k --iodepth=1 --rw=randread --ioengine=windowsaio



fio-2.0.8

Starting 1 thread


read : io=3421.7MB, bw=19615KB/s, iops=4903 , runt=3600001msec

slat (usec): min=0 , max=1688 , avg=10.47, stdev= 5.74




| 1.00th=[ 114], 5.00th=[ 137], 10.00th=[ 149], 20.00th=[ 159],

| 30.00th=[ 171], 40.00th=[ 183], 50.00th=[ 191], 60.00th=[ 199],

| 70.00th=[ 205], 80.00th=[ 217], 90.00th=[ 229], 95.00th=[ 239],

| 99.00th=[ 262], 99.50th=[ 278], 99.90th=[ 446], 99.95th=[ 490],

| 99.99th=[ 556]


lat (usec) : 2=0.01%, 4=0.01%, 10=0.01%, 20=0.01%, 50=0.01%

lat (usec) : 100=0.32%, 250=97.88%, 500=1.76%, 750=0.04%, 1000=0.01%

lat (msec) : 2=0.01%, 4=0.01%, 10=0.01%, 20=0.01%


IO depths : 1=100.0%, 2=0.0%, 4=0.0%, 8=0.0%, 16=0.0%, 32=0.0%, >=64=0.0%

submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%

complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%



READ: io=68958MB, aggrb=19614KB/s, minb=19614KB/s, maxb=19614KB/s,






32

4.2.7 Testing the Mixed Read/Write IOPS (7:3) at 4 KB Data Block

Procedure



Figure 4-7 HioClearData -d 0 command output.

2. Run ./fio --name=ssd --numjobs=4 --filename=\\.\PhysicalDrive1 --bs=4k

--iodepth=64 --rw=randrw --rwmixwrite=30 --ioengine=windowsaio --direct=1

--sync=0 --norandommap --group_reporting --runtime=3600 --time_based in the

directory where the executable file of fio is stored.




NOTE





33

Windows PowerShell



--filename=\\.\PhysicalDrive1 --bs=4k --iodepth=64 --rw=randrw --rwmixwrite=30

--ioengine=windowsaio --direct=1 --sync=0 --norandommap --group_reporting

--runtime=1800 --time_based

lat (msec): 2=20.17%, 4=12.74%, 10=1.54%, 20=0.01%

ssd: (g=0): rw=randrw, bs=4K-4K/4K-4K, ioengine=windowsaio, iodepth=64

...

ssd: (g=0): rw=randrw, bs=4K-4K/4K-4K, ioengine=windowsaio, iodepth=64

fio-2.0.8

Starting 4 threads


read : io=1696.7MB, bw=898762KB/s, iops=224690 , runt=3600003msec

slat (usec): min=0 , max=1000.3K, avg= 9.49, stdev=342.75


lat (usec): min=0 , max=4901.5K, avg=1116.89, stdev=6109.36


| 1.00th=[ 0], 5.00th=[ 113], 10.00th=[ 123], 20.00th=[ 141],

| 30.00th=[ 169], 40.00th=[ 217], 50.00th=[ 322], 60.00th=[ 516],

| 70.00th=[ 828], 80.00th=[ 1384], 90.00th=[ 2320], 95.00th=[ 3664],

| 99.00th=[ 9664], 99.50th=[15552], 99.90th=[43776], 99.95th=[69120],

| 99.99th=[191488]


stdev=57934.67

write: io=2594.2MB, bw=385215KB/s, iops=96303 , runt=3600003msec



lat (usec): min=0 , max=4909.8K, avg=48.08, stdev=919.66


| 1.00th=[ 0], 5.00th=[ 18], 10.00th=[ 22], 20.00th=[ 26],

| 30.00th=[ 28], 40.00th=[ 31], 50.00th=[ 34], 60.00th=[ 37],

| 70.00th=[ 41], 80.00th=[ 46], 90.00th=[ 56], 95.00th=[ 66],

| 99.00th=[ 92], 99.50th=[ 105], 99.90th=[ 139], 99.95th=[ 155],

| 99.99th=[ 209]


lat (usec) : 2=1.56%, 4=0.01%, 10=0.03%, 20=1.48%, 50=23.21%

lat (usec) : 100=4.84%, 250=29.64%, 500=10.76%, 750=5.97%, 1000=4.11%

lat (msec) : 2=9.61%, 4=5.76%, 10=2.35%, 20=0.42%, 50=0.19%

lat (msec) : 100=0.04%, 250=0.02%, 500=0.01%, 750=0.01%, 1000=0.01%

lat (msec) : 2000=0.01%, >=2000=0.01%


IO depths : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0%

submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%

complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.1%, >=64=0.0%



READ: io=3085.7GB, aggrb=898761KB/s, minb=898761KB/s, maxb=898761KB/s,





Performance Test Guide 5 Performance Test on the VMware OS



34

5 Performance Test on the VMware OS


Procedure

1. Install an ES3000 to a PCIe 2.0 x8 slot in an RH2285 V2. The ES3000 is not

hot-swappable. Power off the server before the installation.

2. Power on the server and install VMware ESX 4.1.0 or VMware ESXi 5.0.0.

3. Run lspci | grep Mass to check whether the ES3000 is detected after OS installation.


If Huawei 4th ssd device is displayed, the ES3000 is properly installed. If not, power off the

server and check the SSD card installation.

4. Upload the ES3000 driver to a directory on the VMware OS and run the following

command to install the driver:

VMware ESX 4.1.0: rpm –ivh hio-1.0-0.9.x86_64.rpm

VMware ESXi 5.0.0: esxcli software vib install –v

/HUAWEI_bootbank_hio_1.0-0.8.vib --no-sig-check --maintenance-mode

5. Restart the OS after the driver installation.

6. Run hio_info to check the driver installation. If information similar to following is

displayed, the driver is successfully installed:





35

7. Use the vSphere client to connect the VMware server, choose Configuration >

Hardware > Add Storage, and click Add Storage.

Figure 5-1 Adding a storage device

8. In the Add Storage window, select Disk/LUN, and click Next, as shown in Figure 5-2.

Figure 5-2 Add Storage





36

9. Select the SSD device and click Next, as shown in Figure 5-3.

Figure 5-3 Selecting an SSD device

10. Click Next, as shown in Figure 5-4.

Figure 5-4 VMFS-5





37


Figure 5-5 Current Disk Layout

12. Enter a name for the SSD device and click Next, as shown in Figure 5-6.

Figure 5-6 Entering a name for the SSD device





38

13. Select Maximum available space or specify Custom space setting, and click Next, as

shown in Figure 5-7.

Figure 5-7 Specifying the maximum available space

14. Click Finish, as shown in Figure 5-8.

The virtual disk of the SSD device is created.





39

Figure 5-8 Ready to Complete

The virtual disk is displayed in Datastores, as shown in Figure 5-9.

Figure 5-9 Datastores

15. Use vSphere to create a VM on the VMware server and install Linux or Windows for the

VM.





40

Figure 5-10 Installing an OS for a VM

16. Select a VM, and select Edit virtual machine settings in the right pane, as shown in

Figure 5-11.

Figure 5-11 Edit virtual machine settings

17. In the Virtual Machine Properties window, click Add, as shown in Figure 5-12.





41

Figure 5-12 Virtual Machine Properties

18. Select Hard Disk and click Next, as shown in Figure 5-13.

Figure 5-13 Selecting a hard disk





42


Figure 5-14 Creating a new virtual disk

20. Specify the virtual disk size, select Thick Provision Lazy Zeroed, select Specify a

datastore or datastore cluster, and click Browse, as shown in Figure 5-15.

Figure 5-15 Specifying the virtual disk size





43

21. Select the SSD device, for example Huawei SSD, and click OK, as shown in Figure

5-16.

Figure 5-16 Selecting the SSD device


Figure 5-17 Add Hardware






44

Figure 5-18 Advanced Options

24. Click Finish, as shown in Figure 5-19.

Figure 5-19 Ready to Complete





45

25. Click OK, as shown in Figure 5-20.

Figure 5-20 Adding a new virtual disk complete

26. Start the VM allocated to the new virtual disk. Open the command-line interface (CLI)

and run fdisk –l to check the disk information.

The VM runs Linux in the example.






46

/dev/sdb indicates the virtual disk allocated for the VM.

27. Download the fio software from the website provided in 2.3 "Test Tool" and install the

fio test tool.

An executable fio file is generated.



The performance test on the VMware OS is performed on Linux or Windows of a virtual

machine (VM). For details about the performance test procedure, see 3.2 "Performance Test"

and 4.2 "Performance Test". Note that a virtual disk such as /dev/sdb is to be tested for the

VMs. Therefore, you do not need to run hio_cleardata to clear data on the SSD card.

huawei tecal es3000 high performance pcie ssd card ... ss… · huawei tecal es3000 high...

Documents