Original link:
http://www.eygle.com/special/USE.ORASTRESS.2.TEST.Oracle.db.htm
The author of ORASTRESS! Is Geoff Ingram, which is the author of ORABM, which once I have worked for a few years for Oracle, and the author of the book. The book is now you can download this site. .
About the official website of this tool can be found here:
http://www.linxcel.co.uk/orampm/index.html
ORASTRESS! You can download them in the original website, or choose local download.
The tool is not open source, and the default can only use a session test, you can apply for temporary keys from the author, through the following page we can get a 7-day free-defense limit version:
http://www.linxcel.co.uk/7505/10218_trialkey_orastress!.html
ORASTRESS! Need to run on Windows, you need to install the Oracle client.
After receiving Key, the registration method is as follows:
C: / ORABM> ORASTRESS!
Serial: D5F8-C0A0
After Receiving The Key, Install As Follows by Entering The name and key 通o the dialog box that displays when you run:
C: / ORABM> ORASTRESS! Register
ORASTRESS! The required data is similar to ORABM, you can refer to ORABM installation.
The specific installation steps are as follows:
#
Operation
Command
1
Create the ORABM User (Assums Tools TableSpace, Temp Temporary TableSpace)
SQLPlus system / pwd @orabm_user
2
Create the Tables
SQLPlus system / pwd @orabm_tab
3
Load the data
$ ORABMLOAD WAREHOUSES N
4
Create the indexes
SQLPLUS system / pwd @orabm_ind
5
Analyze the tables and indexes
SQLPlus System / PWD @oramp_analyze
6
Ensure ORABM CAN Run THE DBMS_LOCK PACKAGE
As sys run:
Grant Execute On DBMS_LOCK TO ORABM
Note: If you are 10 WareHouses data, then about 1G space. Here I suggest that 1, 2, 3, 5, 10 WareHouses is performed 1, 2, 4, 6, 10 for single-node databases. A collapsed 50,000-matched test. For multi-node RAC recommends 1,2,3,5,10 WareHouses for 1, 3, 4, 7, 10 concurrent 50,000 transactions tests.
This part of the installation log can refer to: Install the log
After getting test data, you need to run the following script:
Sqlplus ORABM / ORABM @ Your-TNS-Alias> @ oastress_tab.sql
SQLPlus ORABM / ORABM @
SQLPlus ORABM / ORABM @ Your-TNS-Alias> @ ORASTRESS.PLB
Log reference: Windows log
The command line execution is as follows:
ORASTRESS! -S sess-ipeds-list -t transacts-per-sess -c tns-alias-list -m mode [-s batchsize] The following parameters are required: -s Specifies the SESSION number -T Specifies every session execution Quantity.-C Specifies the joint string -m specified running mode. Include READ OLTP INS DIO-S specifies submission of batch for INS or DIO mode, the default is 10,000
Note: If ORASTRESS! Runs a single warehouse in the READ mode, then code execution is the same as ORABM.
For the four operating modes, as follows:
Runs the Identical Read-Only Workload As ORABM To Stress CPU and Memory.
OLTP: Uses all five TPC-C transactions: New-Order, Order-Status, Payment, Stock-Level and Delivery, in order to generate a mixed-transaction (SQL INSERT / UPDATE / DELETE) OLTP workload which stresses CPU, memory, And I / O.
INS: Runs an I / O INTENSIVE SQL Insert Workload by Copying Rows INTO The Item_ins Table from The TPC-C Item Table.
DIO: Runs an I / O INTENSIVE DIRECT-PATH INSERT WORKLOAD BY COPYING ROWS INTO The Item_DIO Table from The TPC-C Item Table.
Here are some operational examples:
EXAMPLE 1:
ORASTRESS! -S 1 -T 50000-C INST1.WORLD -M OLTP
Run ONE ITERATION - COMPRISING 50000 Transactions in 1 session - against instimation.world.
A set of tests, through a session, including 50,000 transactions, test the INST1.WORLD database.
EXAMPLE 2:
ORASTRESS! -S 2 -T 50000-C INST1.WORLD, INST2.WORLD -M OLTP
Run one iteration comprising 2 concurrent sessions of 50000 transactions on each of inst1.world, inst2.world giving a total of 4 concurrent sessions.The location of the instances specified by inst1.world, inst2.world is entirely down to the user. They Could Be:
Run a set of tests, two concurrent sessions each of the two databases (INST1.WORLD, INST2.WORLD), each session runs 50,000 transactions, which can be:
· 2 Instances of A Rac Cluster
· DiffERENT NON RAC Instances on the Same Server
· DiffERENT NON RAC Instances on Different Servers (E.g. One on Linux, One On Solaris)
EXAMPLE 3:
ORASTRESS! -S 1, 2, 4 -T 50000-C INST1, INST2, INST3, INST4 -M READ
Run 3 Items Each of 50000 Transactions on Each of Four Instances: INST1, INST2, INST3 AND INST4, WHERE The Number of Concurrent Sessions in Each Iteration IS: Run 3 groups of tests with 1, 2, 4 concurrent sessions pairs four Example, each executing 50,000 transactions:
1st Iteration: 1 Concurrent Session On Each Instance, Giving 4 Sessions Total
2nd Iteration: 2 Concurrent Sessions on Each Instance, Giving 8 Sessions Total
3RD ITeration: 4 Concurrent Sessions on Each Instance, Giving 16 Sessions
Results Output
- Output results:
ORABM, Showing The Transactions Per second for each session in each ity ity ney ince:
The output is very similar to ORABM, specific reference:
http://www.eygle.com/special/USE.ORABM.2.Test.system.cpu.htm
- Begin Mode = OLTP sess = 1 TXN = 5000 TNS = L fri Sep 19 22:11:06 2003
LXD1.World # 1 w = 3 Txn (all) = 5000 xn (sam) = 3999 t (sam) = 431 TPS = 92.8 end = 190903-12: 25: 39
--- End - Fri Sep 19 22:20:19 2003
Briefly illustrate here:
For Benchmark testing, the most important thing is the standard. If you have a unified model and standard, then the test data has a meaning, otherwise it is not too strong in different concurrency, data is not too significant. .
Standard, comparison, reference, this is the most important for testing.
Here is an article for reference:
Performance test indicator introduction
Some of my test data is given below:
1.10 Warehouse test data
E: / ORADOC / ORACLE ~ 4 / BENCHM ~ 1 / ORASTR ~ 1> "ORASTRESS!. EXE" -S 1 -t 300 -C HSBILL -M OLTP
- Begin Mode = OLTP sess = 1 TXN = 300 TNS = HSBILL THU SEP 30 10:35:09 2004
Hsbill.hurray.com.cn # 1 w = 3 TXN (ALL) = 300 xn (SAM) = 239 t (sam) = 120 TPS = 2 D = 13 (5.4%) n = 102 (42.7%) o = 6 (2.5%) P = 112 (46.9%) s = 6 (2.5%) end =
300904-10: 34: 38
--- End - Thu Sep 30:37:39 2004
E: / ORADOC / ORACLE ~ 4 / BENCHM ~ 1 / ORASTR ~ 1> "ORASTRESS!. EXE" -S 2 -t 300 -C HSBILL -M OLTP
- Begin Mode = OLTP sess = 2 TXN = 300 TNS = HSBILL THU SEP 30 10:41:40 2004HSBILL.HURRAY.com.cn # 1 w = 4 TXN (ALL) = 300 XN (SAM) = 239 t SAM) = 469 TPS = .5 d = 12 (5%) n = 103 (43.1%) o = 13 (5.4%) P = 101 (42.3%) s = 10 (4.2%) end
= 300904-10: 47: 25
Hsbill.hurray.com.cn # 1 w = 4 TXN (ALL) = 300 xn (SAM) = 239 t (sam) = 314 TPS = .8 D = 11 (4.6%) n = 92 (38.5%) o = 10 (4.2%) P = 119 (49.8%) S = 7 (2.9%) end
= 300904-10: 47: 51
--- End - Thu Sep 30 10:50:51 2004
E: / ORADOC / ORACLE ~ 4 / BENCHM ~ 1 / ORASTR ~ 1> "ORASTRESS! .EXE" -S 2 -t 3000 -C HSBILL -M OLTP
--- Begin Mode = OLTP sess = 2 TXN = 3000 TNS = HSBILL THU SEP 30 11:26:02 2004
Hsbill.hurray.com.cn # 1 w = 8 TXN (ALL) = 3000 xn (SAM) = 2399 T (SAM) = 4991 TPS = .5 D = 109 (4.5%) n = 1016 (42.4%) o = 116 (4.8%) P = 1050 (43.8%) s = 108
(4.5%) End = 300904-13: 09: 23
Hsbill.hurray.com.cn # 1 w = 4 TXN (ALL) = 3000 xn (SAM) = 2399 T (SAM) = 5432 TPS = .4 D = 87 (3.6%) n = 997 (41.6%) o = 128 (5.3%) P = 1070 (44.6%) s = 117 (4
.9%) End = 300904-13: 13: 50
--- End - Thu Sep 30 13:16:51 2004
2.5 Warehouse test data
E: / ORADOC / ORACLE ~ 4 / BENCHM ~ 1 / ORASTR ~ 1> "ORASTRESS!. EXE" -S 2 -t 300 -C HSBILL -M OLTP
- Begin Mode = OLTP sess = 2 TXN = 300 TNS = HSBILL THU SEP 30 15:48:20 2004
Hsbill.hurray.com.cn # 1 w = 2 TXN (ALL) = 300 xn (SAM) = 239 t (sam) = 13 TPS = 18.4 D = 7 (2.9%) n = 97 (40.6%) o = 9 (3.8%) P = 119 (49.8%) s = 7 (2.9%) end =
300904-15: 45: 40
Hsbill.hurray.com.cn # 1 w = 5 TXN (ALL) = 300 xn (SAM) = 239 t (sam) = 19 Tps = 12.6 d = 7 (2.9%) n = 97 (40.6%) o = 11 (4.6%) P = 112 (46.9%) s = 12 (5%) end =
300904-15: 45: 47
