Use orastress! To test your database

Original link:


Http://www.eygle.com/special/Use.Orastress.2.Test.Oracle.db.htm



Orastress! 's author is Geoff Ingram, the author of the ORABM we described earlier, who worked for Oracle for several years and was the author of high Performance Oracle "(isbn:0471224367)."
The book now you can download at this site.

The official web page of the tool can be found here:

Http://www.linxcel.co.uk/orabm/index.html

orastress! you can download it from the original website or choose to download it locally.

The tool is not open source, the default can only use a session test, you can apply for the temporary key from the author, through the following page we can get 7 days of the Non-functional Limited use version:

Http://www.linxcel.co.uk/7505/10218_trialkey_orastress!.html

Orastress! need to run on Windows, you need to install Oracle clients.

After the key is received, 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 into the dialog box, which is displays when you run:

c:\orabm>orastress! Register



orastress! needs data similar to ORABM, you can refer to the ORABM installation method.

The specific installation steps are as follows:

#

Operation

Command

1

Create the ORABM user (assumes 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 @orabm_analyze

6

Ensure ORABM can run the Dbms_lock package

As SYS run:

GRANT EXECUTE on Dbms_lock to ORABM

Note: If the 10-warehouses data is built here, then approximately 1G of space is required.
Here I propose to use the 1,2,3,5,10 warehouses for a single node database to 1,2,4,6,10 concurrent 50,000 transaction tests.
For Multi-node RAC It is recommended to use a 1,2,3,5,10 warehouses for 1,3,4,7,10 concurrent 50,000-transaction tests.

This section of the installation log can refer to: installation log

After you get the test data, you need to run the following script:

Sqlplus orabm/orabm@<your-tns-alias> @orastress_tab. sql
Sqlplus orabm/orabm@<your-tns-alias> @orastress. PLH
Sqlplus orabm/orabm@<your-tns-alias> @orastress. PLB

Log reference: Windows log

The command line executes the following ways:

orastress! –s sess-iterations-list–t transacts-per-sess–c tns-alias-list–m mode [-S batchsize]

Here you need the following parameters:
-s Specifies the number of sessions
-t Specifies the number of things that each session executes.
-c Specifies the join string
-m Specifies the mode of operation. including Read OLTP INS DIO
-s Specifies that the bulk is submitted for INS or Dio mode, by default 10000

Note: if orastress! Run in read mode for a single warehouse, then code execution is the same as ORABM.

The description of the four operating modes is as follows:

Read: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 to the Item_ins table from the Tpc-c ITEM table.

Dio:runs an I/O intensive Direct-path INSERT workload by copying rows to the Item_dio table from the Tpc-c ITEM table.

Here are some examples of running:

Example 1:

orastress! –s 1–t 50000–c inst1.world–m OLTP

Run one iteration-comprising 50000 transactions in 1 Session-against inst1.world.
Perform a set of tests that test the Inst1.world database through a session containing 50,000 transactions.

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 are entirely down to the user. They could be:
Run a set of tests that emit two concurrent sessions for each of the two databases (Inst1.world,inst2.world), 50,000 transactions per session, and two databases 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 iterations Each of 50000 transactions to each of four instances:inst1, Inst2, Inst3 and Inst4, where the number of Concurrent sessions in each iteration are:
Run 3 sets of tests, each executing 50,000 transactions for each of the four instances with 1,2,4 concurrent sessions:

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 sessions
Results output--Output Result:
Output is very similar to ORABM, showing the transactions per second as each session in each iteration and the Transactio N split between the five tpc-c transactions for OLTP mode:
The output is very similar to the ORABM, for 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-fri Sep 19 22:20:19 2003



Here is a brief explanation:
For the benchmark test, the most important is the standard, if you have a unified model and standards, then test data also has significance, otherwise, different concurrency, data to carry out the test is not very significant.
Standards, comparisons, references, which are most important for testing.

Here is an article for your reference:

Introduction of performance Test index

Here are some of my test data:

1.1 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 Sep Thu 2004HSBILL. 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% : 34:38---end-thu Sep 10:37:39 2004e:\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 Sep Thu 2004HSBILL. Hurray.com. Cn#1 w=4 Txn (All) =300 xn (SAM) =239 T (SAM) =469 tps=.5 (5%) d=12 (n=103) 43.1% (o=13) 5.4% (p=101) 42.3% (s=10) 4.2% 0:47:25hsbill. 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% 0:47:51---end-thu Sep 10:50:51 2004e:\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 Sep Thu 2004HSBILL. 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% 300904-13:09:23hsbill. 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% 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 Sep Thu 2004HSBILL. 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% : 45:40hsbill. 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% (5) s=12 : 45:47---end-thu Sep 30 15:48:47 2004