关闭

关于Oracle orion存储性能测试工具

标签: oracleorionoracle 11.2
698人阅读 评论(0) 收藏 举报
分类:
关于Oracle orion存储性能测试工具:


注意点:
1. Oracle orion 存储性能测试工具从Oracle database 11gR2开始就自带了.在$GRID_HOME/bin下和$RDBMS_HOME/bin都自带了该工具
2. 在rac环境中,请使用$GRID_HOME/bin下的orion来进行性能测试.


如下全文摘录 orion的help:

[gird@rac1 bin]$ ./orion -help
ORION: ORacle IO Numbers -- Version 11.2.0.4.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' 
parameter.


<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 microseconds.
<testname>_<date>_hist.csv - Histogram of IO latencies.
<testname>_<date>_trace.txt - Extended, unprocessed output.


WARNING: IF YOU ARE PERFORMING WRITE TESTS, BE PREPARED TO LOSE ANY DATA STORED
ON THE LUNS.


Mandatory parameters:
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.


Optional parameters:
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 
			<testname>.lun.


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.  
			No default.


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 
			             IOs.
			  col      - Test a varying large IO load with num_small 
			             small IOs.
			  row      - Test a varying small IO load with num_large 
			             large IOs.
			  max      - Test varying loads up to the num_small and 
			             num_large limits.


hugenotneeded		Tells Orion to allocate regular pages when huge
			pages are not available. With out this option, on systems
			that support hugepages, Orion errors out when it cannot
			allocate sufficient huge pages. -hugenotneeded is not set by
			default.


verbose			Prints tracing information to standard output if set.
			Not set by default.
datainput		Name of the input file for data to be written.


is_lgwr			if set to true will run test using VIP level QOS, assuming the underlying transport supports it.




Examples:
For a preliminary set of data
	-run simple 
For a basic set of data
	-run normal 
To evaluate storage for an OLTP database
	-run oltp 
To evaluate storage for a data warehouse
	-run dss 
To generate combinations of 32KB and 1MB reads to random locations
	-run advanced 
	-size_small 32 -size_large 1024 -type rand 
	-matrix detailed
To generate multiple sequential 1MB write streams, simulating RAID0 striping
	-run advanced 
	-simulate RAID0 -write 100 -type seq
	-matrix col -num_small 0
[gird@rac1 bin]$ 


如下是用法:

第一:
su - grid
第二:
先编辑一下/home/grid/a/xxxtest.lun的内容,如下所示:
[gird@rac1 ~]$ cat /home/grid/a/xxxtest.lun
/dev/highgo/asm-data0101
/dev/highgo/asm-fla1
/dev/highgo/asm-redo1

第三:
cd $ORACLE_HOME/bin/
[gird@rac1 bin]./orion  -run oltp -testname  /home/grid/a/xxxtest

0
0

查看评论
* 以上用户言论只代表其个人观点,不代表CSDN网站的观点或立场
    个人资料
    • 访问:1427748次
    • 积分:22284
    • 等级:
    • 排名:第315名
    • 原创:580篇
    • 转载:261篇
    • 译文:296篇
    • 评论:47条
    博客专栏
    文章分类
    最新评论