Shulou(Shulou.com)06/02 Report--

How to carry out the Istroke O test of the disk

Https://wiki.mikejung.biz/Benchmarking

There are additions and deletions in the translation

1 Linux common benchmarking tools

FIO

Sysbench

Phoronix Test Suite (moved to it's own page)

IOzone

Ioping

UnixBench

Google's Perfkit Benchmarker

2 FIO

Fio is an older io testing tool, written by Jens Axboe.

Home page https://www.thomas-krenn.com/en/wiki/Fio

Installation of fio

My test environment has centos7 redhat5, so I have to download two versions of the fio package.

The redhat5 version needs to be downloaded from the archiving site.

Http://archives.fedoraproject.org/pub/archive/epel/

Download and install rpm-ivh fio-1.57-1.el5.x86_64.rpm

Centos7 can be downloaded from many mirror sites, and the site list can be queried.

Https://admin.fedoraproject.org/mirrormanager/mirrors/EPEL

If the yum source of epel is configured, directly yum install-y fio

Fio test options and examples

The example uses fio to test random writes to the disk

Fio-name=randwrite-ioengine=libaio-iodepth=1-rw=randwrite-bs=4k\

-direct=0-- size=512M-- numjobs=8-- runtime=240-- group_reporting

-- rw=randwrite specifies random write

-- direct=0 specifies whether to use buffered IO or direct IO. If you use buffer, be careful that the total size does not exceed physical memory

-- numjobs=8 starts 8 processes

-- size=512M write 512m per process

Group_reporting aggregates the statistical results of multiple processes to make it easier to read

-- runtime=240 runs continuously for 4 minutes

-bs=4k-blocksize=4k (default)

-- io engines available for ioengine=libaio can be viewed using fio--enghelp (fio-2.2.8)

-- iodepth=1 when testing ssd disks by default, it can be expanded to 32, usually 4 is enough

The iodepth option defines the amount of IO units that will continue to hammer a file with requests during the test.

The way to avoid using buffer is to specify-- direct=1 or write files that are twice as large as physical memory

The focus of the fio results is on projects:

Iops=1416 iops=1416

95.00th = [2] 95% of IO is completed in 2 milliseconds

Busy degree of util=99.62% equipment

The example uses fio to test random reads of disks

Fio-name=randread-ioengine=libaio-iodepth=16-rw=randread-bs=4k\

-direct=0-- size=512M-- numjobs=8-- runtime=240-- group_reporting

Fio help

Man fio

Fio-h

Fio-v

Write options in the fio command line, or you can write command line options to a parameter file job file

After fio is installed, it comes with some samples

# rpm-ql-p fio-1.57-1.el5.x86_64.rpm

/ usr/bin/fio

/ usr/bin/fio_generate_plots

/ usr/share/doc/fio-1.57

/ usr/share/doc/fio-1.57/COPYING

/ usr/share/doc/fio-1.57/HOWTO

/ usr/share/doc/fio-1.57/README

/ usr/share/doc/fio-1.57/REPORTING-BUGS

/ usr/share/doc/fio-1.57/examples

/ usr/share/doc/fio-1.57/examples/1mbs_clients

/ usr/share/doc/fio-1.57/examples/aio-read

.

Aio-read parameter file, which can be used immediately after modification.

# fio aio-read.bak

File1: (Grou0): rw=randread, bs=128K-128K/128K-128K, ioengine=libaio, iodepth=4

File2: (Grou0): rw=randread, bs=128K-128K/128K-128K, ioengine=libaio, iodepth=32

File3: (Grou0): rw=randread, bs=128K-128K/128K-128K, ioengine=libaio, iodepth=8

File4: (Grou0): rw=randread, bs=128K-128K/128K-128K, ioengine=libaio, iodepth=16

Fio 1.57

.

Some comments on the fio output result

Io Number of megabytes of I/O performed.

Bw Average data rate (bandwidth).

Runt Threads run time.

Slat Submission latency minimum, maximum, average and standard deviation. This

Is the time it took to submit the I/O.

Clat Completion latency minimum, maximum, average and standard deviation. This

Is the time between submission and completion.

Bw Bandwidth minimum, maximum, percentage of aggregate bandwidth received, average and standard deviation.

The group statistics show:

Io Number of megabytes I/O performed.

Aggrb Aggregate bandwidth of threads in the group.

Minb Minimum average bandwidth a thread saw.

Maxb Maximum average bandwidth a thread saw.

Mint Shortest runtime of threads in the group.

Maxt Longest runtime of threads in the group.

Finally, disk statistics are printed with reads first:

Ios Number of I/Os performed by all groups.

Merge Number of merges in the I/O scheduler.

Ticks Number of ticks we kept the disk busy.

Io_queue

Total time spent in the disk queue.

Util Disk utilization.

Example Random read Direct IO

Fio-name=randread-ioengine=libaio-iodepth=16-rw=randread-bs=4k-direct=1-size=1G-numjobs=8 runtime=240-group_reporting

If http://blog.csdn.net/yuesichiu/article/details/8722417 doesn't have the patience to read English, the last csdn post translated into Chinese will probably not be finished in Chinese.

3 sysbench

Sysbench can test cpu\ oltp mysql\ fileio there are many articles used to test mysql.

Installation of sysbench

In centos, you can install it directly from epel. Mysql / postgresql is required for installation

Installation method in source text

Wget ftp://ftp.gnome.org/mirror/fedora/epel/6/x86_64/sysbench-0.4.12-5.el6.x86_64.rpm

Wget http://downloads.mysql.com/archives/mysql-5.1/MySQL-shared-compat-5.1.49-1.rhel5.x86_64.rpm

Rpm-iv MySQL-shared-compat-5.1.49-1.rhel5.x86_64.rpm

Yum install postgresql-libs.x86_64

Rpm-iv sysbench-0.4.12-5.el6.x86_64.rpm

Actual installation method

Rpm-ivh http://archives.fedoraproject.org/pub/archive/epel/epel-release-latest-5.noarch.rpm

Or

Rpm-ivh http://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm

Yum install sysbench

Sysbench I-Band O Test

Master the grammar of sysbench first

# sysbench

Missing required command argument.

Usage:

Sysbench [general-options]... Test= [test-options]... Command

General options:

-- num-threads=N number of threads to use [1]

-- max-requests=N limit for total number of requests [10000]

-- max-time=N limit for total execution time in seconds [0]

-- forced-shutdown=STRING amount of time to wait after-- max-time before forcing shutdown [off]

-- thread-stack-size=SIZE size of stack per thread [32K]

-- init-rng= [on | off] initialize random number generator [off]

-- test=STRING test to run

-- debug= [on | off] print more debugging info [off]

-- validate= [on | off] perform validation checks where possible [off]

-- help= [on | off] print help and exit

-- version= [on | off] print version and exit

Compiled-in tests:

Fileio-File I do O test

Cpu-CPU performance test

Memory-Memory functions speed test

Threads-Threads subsystem performance test

Mutex-Mutex performance test

Oltp-OLTP test

Commands: prepare run cleanup help version

Give some orders.

# run a random write test with "--file-extra-flags=direct" random write

Sysbench-test=fileio-file-total-size=4G-file-num=2-file-test-mode=rndwr-max-time=240-max-requests=0-file-block-size=8K num-threads=4 file-extra-flags=direct

Prepare

Run

Cleanup

Sysbench-test=fileio-file-total-size=1G-file-num=10-file-test-mode=rndwr-max-time=240-max-requests=0-file-block-size=8K-file-extra-flags=direct

Or

Random writing

Sysbench-test=fileio-file-total-size=2G-file-num=64 prepare

Sysbench-test=fileio-file-total-size=2G-file-test-mode=rndwr-max-time=240-max-requests=0-file-block-size=4K-file-num=64-num-threads=1 run

For each in 1 4 8 16 32 64; do\

Sysbench-test=fileio-file-total-size=2G-file-test-mode=rndwr-max-time=240-max-requests=0-file-block-size=4K-file-num=64-num-threads=$each run;\

Sleep 10; done

Random reading

Sysbench-test=fileio-file-total-size=2G-file-test-mode=rndrd-max-time=240-max-requests=0-file-block-size=4K-file-num=64-num-threads=1 run

For each in 1 48 16 32 64; do sysbench-test=fileio-file-total-size=2G-file-test-mode=rndrd-max-time=240-max-requests=0-file-block-size=4K-file-num=64-num-threads=$each run; sleep 10; done

Several key points in the test results:

Test results of a virtual machine (openstack)

[root@v-yfb-cos72-sql05 test] # sysbench-test=fileio-file-total-size=4G-file-num=2-file-test-mode=rndwr-max-time=240-max-requests=0-file-block-size=8K-num-threads=4 run

Sysbench 0.4.12: multi-threaded system evaluation benchmark

Running the test with following options:

Number of threads: 4

Extra file open flags: 0

2 files, 2Gb each

4Gb total file size

Block size 8Kb

Number of random requests for random IO: 0

Read/Write ratio for combined random IO test: 1.50

Periodic FSYNC enabled, calling fsync () each 100requests.

Calling fsync () at the end of test, Enabled.

Using synchronous I/O mode

Doing random write test

Threads started!

Time limit exceeded, exiting...

(last message repeated 3 times)

Done.

Operations performed: 0 Read, 14433721 Write, 288270 Other = 14721991 Total

Read 0b Written 110.12Gb Total transferred 110.12Gb (469.84Mb/sec)

+-+ +

| | Field | Type | Null | Key | Default | Extra | |

+-+ +

| | id | int (10) unsigned | NO | PRI | NULL | auto_increment |

| | k | int (10) unsigned | NO | MUL | 0 | |

| | c | char (120) | NO | |

| | pad | char (60) | NO | |

+-+ +

4 rows in set (0.00 sec)

Mysql >

Mysql > select * from sbtest limit 5

+-- +

| | id | k | c | pad |

+-- +

| | 1 | 0 | | qqqqqqqqqqwwwwwwwwwweeeeeeeeeerrrrrrrrrrtttttttttt |

| | 2 | 0 | | qqqqqqqqqqwwwwwwwwwweeeeeeeeeerrrrrrrrrrtttttttttt |

| | 3 | 0 | | qqqqqqqqqqwwwwwwwwwweeeeeeeeeerrrrrrrrrrtttttttttt |

| | 4 | 0 | | qqqqqqqqqqwwwwwwwwwweeeeeeeeeerrrrrrrrrrtttttttttt |

| | 5 | 0 | | qqqqqqqqqqwwwwwwwwwweeeeeeeeeerrrrrrrrrrtttttttttt |

+-- +

5 rows in set (0.00 sec)

For each in 1 4 8 16 32 64; do\

Sysbench-test=oltp-db-driver=mysql-oltp-table-size=10000000\

-mysql-db=sysbench-mysql-user=sysbench-mysql-password=sysbench\

-max-time=240-- max-requests=0-- oltp-read-only-- oltp-skip-trx\

-- oltp-nontrxmode=select-- num-threads=$each run;\

Sleep 10; done

Sysbench-test=oltp-db-driver=mysql-oltp-table-size=10000000\

-mysql-db=sysbench-mysql-user=sysbench-mysql-password=sysbench\

-max-time=240-- max-requests=0-- oltp-read-only-- oltp-skip-trx\

-oltp-nontrx-mode=select-num-threads=2 run

4 Phoronix Test Suite

The Phoronix test suite is referred to as pts. Download the installation package phoronix-test-suite-7.0.1.tar.gz from the official website http://phoronix-test-suite.com/?k=downloads.

The installation of pts depends on multiple packages such as php-cli

Tar xvf phoronix-test-suite_6.2.2.tar.gz

Cd phoronix-test-suite/

. / install-sh

/ usr/bin/phoronix-test-suite list-available-suites

/ usr/bin/phoronix-test-suite list-available-tests

Phoronix-test-suite info pts/disk

Phoronix-test-suite install pts/iozon

Phoronix-test-suite install pts/disk

Pts/disk includes many tools such as fio iozone aio-stress. PTS is too large, and install takes a long time because of the network speed. Only one iozone is used for a test here.

Run iozone using the pts suite

[root@node1 ~] # phoronix-test-suite run pts/iozone-1.8.0

IOzone 3.405:

Pts/iozone-1.8.0

Disk Test Configuration

1: 4Kb

2: 64Kb

3: 1MB

4: Test All Options

Record Size: 1

1: 512MB

2: 2GB

3: 4GB

4: 8GB

5: Test All Options

File Size: 4

1: Write Performance

2: Read Performance

3: Test All Options

Disk Test: 1

Phoronix Test Suite v6.6.0

System Information

Hardware:

Processor: Intel Core i7-3537U @ 2.49GHz (1 Core), Motherboard: Oracle VirtualBox v1.2, Chipset: Intel 440FX-82441FX PMC, Memory: 4096MB, Disk: 72GB VBOX HDD, Graphics: InnoTek VirtualBox, Audio: Intel 82801AA AC 97 Audio, Network: Intel 82540EM Gigabit

Software:

OS: Oracle Linux Server 7. 3, Kernel: 4.1.12-61.1.18.el7uek.x86_64 (x86: 64), Compiler: GCC 4.8.5 20150623, File-System: xfs, System Layer: KVM VirtualBox

Would you like to save these test results (YBO): y

Enter a name to save these results under: tmp

Enter a unique name to describe this test run / configuration: tmp

If desired, enter a new description below to better describe this result set / system configuration under test.

Press ENTER to proceed without changes.

Current Description: KVM VirtualBox testing on Oracle Linux Server 7.3 via the Phoronix Test Suite.

New Description:

IOzone 3.405:

Pts/iozone-1.8.0 [Record Size: 4Kb-File Size: 8GB-Disk Test: Write Performance]

Test 1 of 1

Estimated Trial Run Count: 3

Estimated Time To Completion: 22 Minutes (04:14 CDT)

Started Run 1 @ 03:53:01

Started Run 2 @ 04:11:11

Started Run 3 @ 04:22:17 [Std. Dev: 108.27%]

Started Run 4 @ 04:26:15 [Std. Dev: 83.68%]

Started Run 5 @ 04:29:54 [Std. Dev: 69.61%]

Started Run 6 @ 04:33:32 [Std. Dev: 60.77%]

Test Results:

8.509765625

14.8359375

69.3681640625

74.802734375

74.82421875

76.93359375

Average: 53.21 MB/s

Do you want to view the results in your web browser (YBO): n

Would you like to upload the results to OpenBenchmarking.org (YBO): n

Run iozone separately

# find /-name iozone

/ var/lib/phoronix-test-suite/installed-tests/pts/iozone-1.8.0/iozone3_405/src/current/iozone

/ var/lib/phoronix-test-suite/installed-tests/pts/iozone-1.8.0/iozone

# cd / var/lib/phoronix-test-suite/installed-tests/pts/iozone-1.8.0/

# export LOG_FILE=1.log

#. / iozone-Ra-g 8G-I 0-b iozone.xls

Referenc

Http://phoronix-test-suite.com/documentation/phoronix-test-suite.html#GettingStarted

Https://wiki.mikejung.biz/Phoronix_Test_Suite

5 installation and use of IOzone

The official website http://iozone.org/

Official help documentation IOzone_msword_98.doc

Download the installation package [Stable tarball] iozone3_465.tar

Installation process

150 mkdir test_iozone

151 mv iozone3_465.tar test_iozone/

152 cd test_iozone/

153 ls

154tar-xf iozone3_465.tar

155 cd iozone3_465/src/current/

156 ls

157 make

158 uname-a

159 make linux-AMD64

160 yum provides cc

161yum install-y gcc

162 make linux-AMD64

163 ll

164ls-ort

165 date

166 iozone

167. / iozone

168. / iozone-h

/ iozone-Ra-g 8G-I 0-b iozone.xls this is output to the xls file

Run command

. / iozone-Ra-g 8G-I 0 this output to the screen

The results of iozone show intuitively the impact of different block sizes and file sizes on IO.

7 installation and use of apt-get install make gcc for UnixBench

Wget https://byte copyright unixbench.googlecode.com Unix benchmark 6.1.3.tgz

Tar zxvf UnixBench6.1.3.tgz

Cd UnixBench

Make

. / Run-I 1

Download UnixBench6.1.3.tgz from

Https://code.google.com/archive/p/byte-unixbench/downloads

255 tar-xzf UnixBench6.1.3.tgz

256 ls

257 cd UnixBench

258 ls

259 make

260 ls-ort

261. / Run-I 1

262 which perl

263 yum install-y perl

[root@v-yfb-cos72-sql05 UnixBench] #. / Run-I 1

Make all

Make [1]: Entering directory `/ root/UnixBench'

Checking distribution of files

. / pgms exists

. / src exists

. / testdir exists

. / tmp exists

. / results exists

Make [1]: Leaving directory `/ root/UnixBench'

Sh: 3dinfo: command not found

# # #

# # #

# # #

# # #

# # #

# # #

Version 5.1.3 Based on the Byte Magazine Unix Benchmark

Multi-CPU version Version 5 revisions by Ian Smith

Sunnyvale, CA, USA

January 13, 2011 johantheghost at yahoo period com

.

=

BYTE UNIX Benchmarks (Version 5.1.3)

System: v-yfb-cos72-sql05.novalocal: GNU/Linux

OS: GNU/Linux-- 3.10.0-327.el7.x86_64-- # 1 SMP Thu Nov 19 22:10:57 UTC 2015

Machine: x86'64 (x86'64)

Language: en_US.utf8 (charmap= "UTF-8", collate= "UTF-8")

CPU 0: Intel Core Processor (Haswell, no TSX) (4600.0 bogomips)

X86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET

CPU 1: Intel Core Processor (Haswell, no TSX) (4600.0 bogomips)

X86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET

06:01:21 up 78 days, 3:34, 1 user, load average: 0.11,0.04,0.05; runlevel 3

Benchmark Run: Thu May 04 2017 06:01:21-06:08:05

2 CPUs in system; running 1 parallel copy of tests

Dhrystone 2 using register variables 29114714.8 lps (10.0s, 1 samples)

Double-Precision Whetstone 3660.1 MWIPS (9.8s, 1 samples)

Execl Throughput 3227.4 lps (29.1s, 1 samples)

File Copy 1024 bufsize 2000 maxblocks 962272.0 KBps (30.0s, 1 samples)

File Copy 256 bufsize 500 maxblocks 256736.0 KBps (30.0s, 1 samples)

File Copy 4096 bufsize 8000 maxblocks 2537028.0 KBps (30.0s, 1 samples)

Pipe Throughput 1282585.0 lps (10.0s, 1 samples)

Pipe-based Context Switching 284899.6 lps (10.0s, 1 samples)

Process Creation 9563.0 lps (30.0s, 1 samples)

Shell Scripts (1 concurrent) 6315.2 lpm (60.0s, 1 samples)

Shell Scripts (8 concurrent) 1360.1 lpm (60.0s, 1 samples)

System Call Overhead 2215239.6 lps (10.0s, 1 samples)

System Benchmarks Index Values BASELINE RESULT INDEX

Dhrystone 2 using register variables 116700.0 29114714.8 2494.8

Double-Precision Whetstone 55.0 3660.1 665.5

Execl Throughput 43.0 3227.4 750.6

File Copy 1024 bufsize 2000 maxblocks 3960.0 962272.0 2430.0

File Copy 256 bufsize 500 maxblocks 1655.0 256736.0 1551.3

File Copy 4096 bufsize 8000 maxblocks 5800.0 2537028.0 4374.2

Pipe Throughput 12440.0 1282585.0 1031.0

Pipe-based Context Switching 4000.0 284899.6 712.2

Process Creation 126.0 9563.0 759.0

Shell Scripts (1 concurrent) 42.4 6315.2 1489.4

Shell Scripts (8 concurrent) 6.0 1360.1 2266.8

System Call Overhead 15000.0 2215239.6 1476.8

=

System Benchmarks Index Score 1400.8

Benchmark Run: Thu May 04 2017 06:08:05-06:14:49

2 CPUs in system; running 2 parallel copies of tests

Dhrystone 2 using register variables 58393583.7 lps (10.0s, 1 samples)

Double-Precision Whetstone 7356.6 MWIPS (9.8s, 1 samples)

Execl Throughput 7037.2 lps (29.9s, 1 samples)

File Copy 1024 bufsize 2000 maxblocks 1368114.0 KBps (30.0s, 1 samples)

File Copy 256 bufsize 500 maxblocks 390873.0 KBps (30.0s, 1 samples)

File Copy 4096 bufsize 8000 maxblocks 3596554.0 KBps (30.0s, 1 samples)

Pipe Throughput 2688283.4 lps (10.0s, 1 samples)

Pipe-based Context Switching 572723.9 lps (10.0s, 1 samples)

Process Creation 22877.0 lps (30.0s, 1 samples)

Shell Scripts (1 concurrent) 9545.3 lpm (60.0s, 1 samples)

Shell Scripts (8 concurrent) 1391.3 lpm (60.0s, 1 samples)

System Call Overhead 3284659.7 lps (10.0s, 1 samples)

System Benchmarks Index Values BASELINE RESULT INDEX

Dhrystone 2 using register variables 116700.0 58393583.7 5003.7

Double-Precision Whetstone 55.0 7356.6 1337.6

Execl Throughput 43.0 7037.2 1636.6

File Copy 1024 bufsize 2000 maxblocks 3960.0 1368114.0 3454.8

File Copy 256 bufsize 500 maxblocks 1655.0 390873.0 2361.8

File Copy 4096 bufsize 8000 maxblocks 5800.0 3596554.0 6201.0

Pipe Throughput 12440.0 2688283.4 2161.0

Pipe-based Context Switching 4000.0 572723.9 1431.8

Process Creation 126.0 22877.0 1815.6

Shell Scripts (1 concurrent) 42.4 9545.3 2251.2

Shell Scripts (8 concurrent) 6.0 1391.3 2318.8

System Call Overhead 15000.0 3284659.7 2189.8

=

System Benchmarks Index Score 2394.8

[root@v-yfb-cos72-sql05 UnixBench] #

[root@node1 UnixBench] #. / Run-I 1

Make all

Make [1]: Entering directory `/ root/UnixBench'

Checking distribution of files

. / pgms exists

. / src exists

. / testdir exists

. / tmp exists

. / results exists

Make [1]: Leaving directory `/ root/UnixBench'

Sh: 3dinfo: command not found

# # #

# # #

# # #

# # #

# # #

# # #

Version 5.1.3 Based on the Byte Magazine Unix Benchmark

Multi-CPU version Version 5 revisions by Ian Smith

Sunnyvale, CA, USA

January 13, 2011 johantheghost at yahoo period com

. This tool is not just a test of Ihand O.

8 installation and use of ioping

Download ioping-0.8.tar.gz

Wget https://ioping.googlecode.com/files/ioping muri 0.8.tar.gz

Tar zxvf ioping-0.8.tar.gz

Cd ioping-0.8/

Make

Make install

. / ioping-c 1000 / home/

# # To run ioping in current directory

. / ioping-c 1000.

# # run ioping with direct I/O

. / ioping-D-c 1000.

#. / ioping-D-c 10.

4.0 KiB from. (xfs / dev/mapper/centos-root): request=1 time=2.7 ms

4.0 KiB from. (xfs / dev/mapper/centos-root): request=2 time=330 us

4.0 KiB from. (xfs / dev/mapper/centos-root): request=3 time=382 us

4.0 KiB from. (xfs / dev/mapper/centos-root): request=4 time=383 us

4.0 KiB from. (xfs / dev/mapper/centos-root): request=5 time=451 us

4.0 KiB from. (xfs / dev/mapper/centos-root): request=6 time=280 us

4.0 KiB from. (xfs / dev/mapper/centos-root): request=7 time=435 us

4.0 KiB from. (xfs / dev/mapper/centos-root): request=8 time=292 us

4.0 KiB from. (xfs / dev/mapper/centos-root): request=9 time=241 us

4.0 KiB from. (xfs / dev/mapper/centos-root): request=10 time=309 us

-. (xfs / dev/mapper/centos-root) ioping statistics-

10 requests completed in 9.0 s, 1.7 k iops, 6.8 MiB/s

Min/avg/max/mdev = 241 us / 576 us / 2.7 ms / 697 us

Note that the above unit of time microsecond (us) = 1G 1000000 seconds ms (millisecond) = 1max 1000 seconds

The following quotes Chu Ba's summary of the performance must-know number "using new hardware to improve database performance. Pptx"

L1 cache reference

0.5 ns

Branch mispredict

5 ns

L2 cache reference

7 ns

Mutex lock/unlock

25 ns

Main memory reference

100 ns

Compress 1K bytes with Zippy

3000 ns

Send 2K bytes over 1 Gbps network (20 microseconds)

20000 ns

Read 1 MB sequentially from memory

250000 ns

Round trip within same datacenter

500000 ns

Disk seek (10 milliseconds 10 ms)

10000000 ns

Read 1 MB sequentially from disk

20000000 ns

Send packet CA- > Netherlands- > CA (150ms)

150000000 ns

Nanoseconds (ns) = 1,000,000,000 seconds

9 PerfKitBenchmarker

Reference https://wiki.mikejung.biz/Google_PerfKitBenchmarker

This is not tested.

Apt-get install git python-pip python-dev unzip openjdk-7-jre

Git clone https://github.com/GoogleCloudPlatform/PerfKitBenchmarker.git

Cd PerfKitBenchmarker/

Pip install-r requirements.txt

Performance Analysis of disk Ihamdo O at 10 AIX

Https://www.ibm.com/developerworks/cn/aix/library/1203_weixy_aixio/index.html

Table 1. Common disk types and their IOPS

Http://en.wikipedia.org/wiki/IOPS

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.