Oracle internals, debugging and undocumented features
Apparently Oracle included this tool into 11g release 2 database.Orion binary is located under $ORACLE_HOME/bin .
Quick run with help command will give very detail explanation how to use this tool.Also
Kevin Closson’s Oracle blog got post about Orion:
-bash-3.2$ orion -help
ORION: ORacle IO Numbers — Version 220.127.116.11.0
ORION runs IO performance tests that model Oracle RDBMS IO workloads.
It measures the performance of small (2-32K) IOs and large (128K+) IOs
at various load levels.
Each Orion data point is a test for a specific mix of small and large
IO loads sustained for a duration. An Orion test consists of multiple
data point tests. These data point tests can be represented as a
two-dimensional matrix. Each column in the matrix represents data
point tests with the same small IO load, but varying large IO loads.
Each row represents data point tests with the same large IO load, but
varying small IO loads. An Orion test can be for a single point, a
single row, a single column, or the whole matrix.
The ‘run’ parameter is the only mandatory parameter. Defaults
are indicated for all other parameters. For additional information on
the user interface, see the Orion User Guide.
<testname> is the prefix used for all input and output filenames. By
default, it is ‘orion’. It can be specified with the ‘testname’
<testname>.lun should contain a carriage-return-separated list of LUNs.
The output files for a test run are prefixed by <testname>_<date> where
date is “yyyymmdd_hhmm”.
The output files are:
<testname>_<date>_summary.txt – Summary of the input parameters, along with
the minimum small IO latency (in usecs), the maximum
MBPS, and the maximum IOPS observed.
<testname>_<date>_mbps.csv – Performance results of large IOs in MBPS.
<testname>_<date>_iops.csv – Performance results of small IOs in IOPS.
<testname>_<date>_lat.csv – Latency of small IOs (in usecs).
<testname>_<date>_trace.txt – Extended, unprocessed output.
WARNING: IF YOU ARE PERFORMING WRITE TESTS, BE PREPARED TO LOSE ANY DATA STORED
ON THE LUNS.
run Type of workload to run (simple, normal, advanced, dss, oltp).
simple – Tests random small (8K) IOs at various loads,
then random large (1M) IOs at various loads.
normal – Tests combinations of random small (8K) IOs and
random large (1M) IOs.
advanced – Tests the workload specified by the user
using optional parameters.
dss – Tests with random large (1M) IOs at increasing
loads to determine the maximum throughput.
oltp – Tests with random small (8K) IOs at increasing
loads to determine the maximum IOPS.
testname Name of the test run.
num_disks Number of disks (physical spindles). This number is
used to gauge the range of loads that Orion should test
at. Increasing this parameter results in Orion using
heavier IO loads. Default is the number of LUNs in
size_small Size of small IOs in KB. Default is 8.
size_large Size of large IOs in KB. Default is 1024.
type Type of large IOs (rand, seq). Default is rand.
rand – Randomly distributed large IOs.
seq – Sequential streams of large IOs.
num_streamIO Number of concurrent IOs per stream. This parameter is only
used if -type is seq. Default is 4.
simulate Orion tests on a virtual LUN formed by combining the
specified LUNs in one of these ways. This parameter is
typically only used if -type is seq. Default is concat.
concat – A serial concatenation of the LUNs. Each
sequential stream issues IOs to only one LUN.
raid0 – A RAID-0 mapping across the LUNs. Each
sequential stream issues IOs across all LUNs,
using RAID-0 striping.
write Percentage of IOs that are writes (SEE WARNING ABOVE).
Default is 0.
cache_size Size in MBs of the array’s cache.
Unless this option is set to 0, Orion issues a number
of unmeasured, random IOs before each large sequential
data point. These IOs fill up the storage array’s cache
(if any) with random data so that IOs from one
data point do not result in cache hits for the next
data point. Read tests are preceded with junk reads
and write tests are preceded with junk writes. If
specified, this ‘cache warming’ is performed until
cache_size MBs of IO have been read or written.
Default behavior is to issue 2 minutes of unmeasured random
IOs before each data point.
duration Duration of each data point in seconds. Default is 60.
num_small Number of outstanding small IOs. This parameter controls the
small IO load. Only used if -matrix is point, col, or max.
num_large This parameter controls the large IO load.
For -type rand, number of outstanding large IOs.
For -type seq, number of sequential IO streams. Only used
if -matrix is point, row, or max. No default.
matrix An Orion test consists of multiple data point tests. These data
point tests can be represented as a two-dimensional matrix.
Each column in the matrix represents data point tests with
the same small IO load, but varying large IO loads. Each
row represents data point tests with the same large IO load,
but varying small IO loads. An Orion test can be for a
single point, a single row, a single column, or the whole
matrix, depending on the matrix option setting below.
Default is basic.
basic – Test small IOs only, then large IOs only.
detailed – Test entire matrix.
point – Test with num_small small IOs, num_large large
col – Test a varying large IO load with num_small
row – Test a varying small IO load with num_large
max – Test varying loads up to the num_small and
verbose Prints tracing information to standard output if set.
Not set by default.
For a preliminary set of data
For a basic set of data
To evaluate storage for an OLTP database
To evaluate storage for a data warehouse
To generate combinations of 32KB and 1MB reads to random locations
-size_small 32 -size_large 1024 -type rand
To generate multiple sequential 1MB write streams, simulating RAID0 striping
-simulate RAID0 -write 100 -type seq
-matrix col -num_small 0