OracleORION: Storage System Performance Testing Tool

ORION (OracleIOCalibrationTool) is a bottleneck provided by Oracle to test the performance of the storage system. Because ORION is an independent tool, you do not need to create and

ORION (Oracle I/O Calibration Tool) is provided by Oracle to test the performance bottleneck of the storage system. Because ORION is an independent Tool, you do not need to create and

(I) Definition

ORION (Oracle I/O Calibration Tool) is a bottleneck provided by Oracle for testing storage system performance.
As ORION is an independent tool, you do not need to create or run an Oracle database.
ORION is very simple to use. You can directly decompress the downloaded package from the official website.


Decompress:
# Gunzip orion_linux_x86.gz


(Ii) Advantages

● You do not need to run Load Runner or configure a large number of virtual users.
● You do not need to run the Oracle database or prepare a large amount of test data.
● 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
● You can customize a certain proportion of write operations as needed (no write operations by default). However, note that if there is data on the disk, be careful when the data is overwritten.


(Iii) output file

At the end of the ORION execution, five files will be output:
● _Summary.txt-Summary of the input parameters along with min. small latency, max large MBPS and/or max. small IOPS.
● _Mbps.csv-Performanceresults of large IOs in MBPS (throughput)
● _Iops.csv-Performanceresults of small IOs in IOPS (IO times per second)
● _Lat.csv-Latency of smallIOs (Response Time)
● _Tradeoff.csv-Shows largeMBPS/small IOPS combinations that can be achieved at certain small latencies
● _Trace.txt-Extended, unprocessed output (trace information, the most detailed data)


(4) three mandatory parameters

Running ORAION must contain three parameters: run, testname, and num_disks.
● 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)


(V) A simple test

ORION execution requires a parameter file to specify the disk for testing.
# Cat/dev/sda1> rocky
# Cat/dev/sda2> rocky
#./Orion_linux_x86-run simple-testname rocky-num_disks 1
The test results generate the five files mentioned above.