Oracle Orion I/O Testing Tool

 

1. Orion Overview 1.1 Orion description

Orion (Oracle I/O calibration tool) is an independent tool used to calibrate the I/O performance of the Oracle database's storage system. The calibration result is of great help for understanding the performance of the storage system. It can not only identify the problems affecting the performance of the Oracle database, but also measure the size of the new database installation. As Orion is an independent tool, you do not need to create and run Oracle databases.

Orion:
Http://www.oracle.com/technology/global/cn/software/tech/orion/index.html

 

To simulate the Oracle database as much as possible, Orion uses the same I/O software set as Oracle to generate a combined I/O load. You can configure Orion to generate many I/O loads, including an I/O load that simulates OLTP and data warehouse loads.

Orion supports multiple platforms. More platforms will be supported in the future. The User Guide provides detailed user guides, including "Getting started" and troubleshooting instructions. You can call the "-help" option in Orion to directly obtain the abstract about how to use Orion.

Note that Oracle does not support Orion.

 

Advantages:

1. Do not need to run Load Runner and configure a large number of clinet

2. You do not need to run the Oracle database or prepare a large amount of test data.

3. The test results are more representative. For example, in random I/O testing, the software can make the storage hit rate close to 0, and simulate the real iops of the disk, however, it is difficult for the load runner to achieve this, and the final disk iops needs to be converted.

4. You can customize a certain proportion of write operations as needed (no write operations by default). However, note that if data exists on the disk, be careful when overwriting the data.

 

Disadvantages

1. Up to now, the custom overall running time and pressurization range cannot be specified, which is completely automatic here.

2. Some custom operation types cannot be performed, such as table scan and load testing. However, this effect can be achieved by combining with the Oracle database.

 

1.2 Orion help

C: \ Program Files (x86) \ oracle \ Orion> Orion-help

Orion: Oracle Io numbers -- version10.2.0.1.0

Orion runs Io performance tests that modeloracle RDBMS Io workloads.

It measures the performance of small (2-32 K) iOS and large (128 K +) iOS at various load levels. each Orion data point is done at a specific mixof small and large Io loads sustained for a duration. anywhere from a single data point to ATwo-dimen1_array of data points can be tested by setting the rightoptions.

 

An Orion test consists of data points atvarous small and large Io load levels. these points can be represented as a two-dimenstmmatrix: Each columnin the matrix represents a fixed small Io load. each row represents a fixedlarge Io load. the first row is with no largeio load and the first column is with no small Io load. an Orion test can be a single point, a row, Acolumn or the whole matrix.

 

Parameters 'run', 'testname', and 'num _ disks 'are mandatory. defaults are indicated for all otherparameters. For additional information on the user interface, see the Orion user guide.

-- Running oraion must contain three parameters: Run, testname, and num_disks.

 

<Testname>. Lun shoshould contain acarriage-return-separated list of Luns the output files for a test run areprefixed by <testname> _.

 

The output files are:

<Testname> _summary.txt-Summary ofthe input parameters along with Min. Small latency, Max large Mbps and/or Max. Small iops.

<Testname> _mbps.csv-performanceresults of large iOS in Mbps (throughput)

<Testname> _iops.csv-performanceresults of small iOS in iops (IO times per second)

<Testname> _lat.csv-latency of smallios (Response Time)

<Testname> _tradeoff.csv-shows largembps/small iops combinations that can be achieved at certain small latencies

<Testname> _trace.txt-extended, unprocessed output (trace information, the most detailed data)

-- After the execution of Orion, five files are output. For the different functions of each file, see the preceding description.

 

Warning: if you are using Ming write tests, be prepared to lose any data stored on the Luns.

 

Mandatory parameters (mandatory parameter description ):

Run type of workload to run (simple, normal, advanced)

Simple-Tests random 8 K small IOS at various loads, then random 1 m largeios at various loads.

Normal-Tests combinations of random8k small iOS and random 1 m large IOS

Advanced-run theworkload specified by the user using optional parameters

Testname name of the test run

Num_disks Number of disks (physicalspindles)

 

Optional parameters (optional parameter description, note the default value ):

Size_small size of small IOs (in KB)-default 8

Size_large size of large IOs (in KB)-default 1024

Type type of large IOs (RAND, SEQ)-default Rand

Rand-random largeios

SEQ-sequential streams of large IOS

Num_streamio number of concurrent IOS per stream (only if type is SEQ)-default 4

Simulate Orion tests on a virtual volumeformed by combining the provided volumes in one of these ways (default Concat ):

Concat-A serialconcatenation of the volumes

Raid0-A RAID-0mapping against ss the volumes

Write percentage of writes (seewarning above)-default 0

Cache_size size * in megabytes * of thearray's cache.

Unless this option is set to 0, Orion does anumber of (unmeasured) random Io before each large sequential data point. this is done in order to fill up the array cachewith random data. this way, the blocksfrom one data point do not result in cache hits for the next data point. read tests are preceded with junk reads andwrite tests are preceded with junk writes. if specified, this 'cache warming' is done until cache_size worth of iohas been read or written.

Default behavior: fillup cache for 2 minutes before each data point.

Duration duration of each data point (inseconds)-default 60

Num_small number of outstanding small IOs (only if matrix is point, Col, or Max)-No Default

Num_large for random, number ofoutstanding large IOS.

For sequential, numberof streams (only if matrix is point, row, or Max)-nodefault

Matrix an Orion test consists ofdata points at various small and large Io load levels. these points can be represented as ATwo-dimen1_matrix: each column in the matrix represents a fixed small ioload. each row represents a fixed largeio load. the first row is with no largeio load and the first column is with no small Io load. an Orion test can be a single point, a row, Acolumn or the whole matrix, depending on the matrix option setting below (default basic ):

Basic-test thefirst row and the first column

Detailed-test theentire Matrix

Point-test at loadlevel num_small, num_large

Col-varying largeio load with num_small small IOS

Row-varying smallio load with num_large large IOS

Max-test varyingloads up to num_small, num_large

Verbose prints tracing information tostandard output if set.

Default -- not set

 

Examples

For a preliminary set of data

-Run simple-testname <Name>-num_disks <#>

For a basic set of data

-Run normal-testname <Name>-num_disks <#>

To generate combinations of 32kb and 1 mbreads to random locations:

-Run advanced-testname <Name>-num_disks <#>

-Size_small 32-Si ze_large 1024-type rand-matrix detailed

To generate multiple sequential 1 MB writestreams, simulating 1 MB raid0 stripes

-Run advanced-testname <Name>-num_disks <#>

-Simulate raid0-stripe 1024-write 100-type seq

-Matrix col-num_small 0

 

C: \ Program Files (x86) \ oracle \ Orion>

 

 

Ii. Usage in Windows

2.1 create the Dave. Lun file in the Orion installation directory and add the partitions to be tested, for example:

\. \ D:

Here we want to test disk D.

2.2 run the Orion command.

Orion has three different levels: simple, normal, and advance. You can set this level based on your needs. For example:

C: \ Program Files (x86) \ oracle \ Orion> Orion-runsimple-testname Dave-num_disks 1

-- Note that the testname parameter only needs to write the file name. Orion will automatically add the extension. If the extension is written, an error will be reported.

Orion: Oracle ionumbers -- version 10.2.0.1.0

Test will takeapproximately 9 minutes

Larger cachesmay take longer

 

Testname indicates the name of the Lun file we configured earlier. num_disks indicates the number of disks.

 

2.3 view results

In the Orion installation directory, several files are generated: dave_iops.csv1_dave_lat.csv1_dave_mbps.csv; dave_summary.txt and dave_trace.txt. Let's take a look at the contents of summary.

 

Orion version10.2.0.1.0

 

CommandLine:

-Run simple-testname Dave-num_disks 1

 

This maps tothis test:

Test: Dave

Small Io size: 8 KB

Large Io size: 1024 KB

Io types: smallrandom iOS, large random IOS

Simulated arraytype: Concat

Write: 0%

Cache size: notentered

Duration foreach data point: 60 seconds

Smallcolumns:, 0

Largecolumns:, 0, 1, 2

Total datapoints: 8

 

Name: \. \ D: Size: 1784847360

1 files found.

 

Maximum largembps = 32.83 @ small = 0 and large = 1

Maximum smalliops = 74 @ small = 2 and large = 0

Minimum smalllatency = 13.53 @ small = 1 and large = 0

 

Because the test result is a CSV file, you can easily draw a pressure curve in excle based on the results.

 

Iii. Usage in Linux

3.1 decompress Orion

Decompress the software with the root user:

Unzip orion_linux_x86-64.gz

After decompression, generate Orion software: orion_linux_x86-64

 

3.2 configure the Dave. Lun file. For example:

/Dev/sdc1

/Dev/sdd1

/Dev/sde1

/Dev/sdf1

 

3.3 run the Orion command:

Orion_linux_x86-64-run simple-testname Dave-num_disks 4

-- Note that the testname parameter only needs to write the file name. Orion will automatically add the extension. If the extension is written, an error will be reported.

 

3.4 view results

 

 

4. Other test command examples

4.1 database OLTP type, assuming all Io types are 8 K random operation, pressure type, automatic pressurization, from small to large, to the storage pressure limit

#./Orion-run advanced-testname dave-num_disks 1-size_small 8-size_large 8-type Rand &

 

4.2 database throughput test, assuming I/O is all 1 m sequential I/O

#./Orion-run advanced-testname mytest-num_disks 96-size_small 1024-size_large 1024-type seq &

 

4.3. Specify a specific IO type and I/O pressure. For example, when a small Io is set to 500, the pressure varies with the large Io.

#./Orion-run advanced-testname mytest-num_disks 96-size_small 8-size_large 128-matrix col-num_small 500-typerand &

 

4.4. Test the pressure matrix based on different Io types

#./Orion-run advanced-testname mytest-num_disks 96-size_small 8-size_large 128-matrix detailed-type Rand &

 

 

 

 

 

 

Bytes -------------------------------------------------------------------------------------------------------

All rights reserved. reprinted articles are allowed, but source addresses must be indicated by links. Otherwise, the documents will be held legally responsible!

Blog: http://blog.csdn.net/tianlesoftware

WEAVER: http://weibo.com/tianlesoftware

Email: tianlesoftware@gmail.com

Skype: tianlesoftware

 

------- Add a group to describe the relationship between Oracle tablespace and data files in the remarks section. Otherwise, reject the application ----

Dba1 group: 62697716 (full); dba2 group: 62697977 (full) dba3 group: 62697850 (full)

Super DBA group: 63306533 (full); dba4 group: 83829929 (full) dba5 group: 142216823 (full)

Dba6 group: 158654907 (full) dba7 group: 69087192 (full) dba8 group: 172855474

DBA super group 2: 151508914 dba9 group: 102954821 chat group: 40132017 (full)