Oracle's performance Testing experience summary

Some time ago, in Ali mother new room pressure test process used in the LR test Oracle, with the DBA (landlords) in Hangzhou netcom New computer room for 1000 users of the pressure simulation test. The entire stress test takes two days. The following are some of the experiences:

1 The stress test process found that some of the SQL scripts performed very slowly and were optimized.

2 The best concurrent testing, otherwise the service is basically no pressure.

3 Start from 100 users, and then slowly up, until the CPU load up to more than 90%. View the performance of the system, including TPS, response time, and memory.

It also includes the I/O traffic and the number of transactions for the Oracle server.

This plan is to refer to Taobao Room performance test plan, the following is the specific steps of performance testing:

Oracle's performance testing is mainly to simulate a large number of SQL statement operations, to pressure the database server. Before testing, you need to prepare the following SQL statements to simulate, test the script, and prepare the test controller, the test press, and the database server being tested.

The Scripting Protocol selects Oracle (2-tier), puts all SQL statements to be emulated in one SQL file, uses Sql-plus to manipulate the database load, and uses LoadRunner to record. After recording, you modify the script, first define the variable in the vdf.h file (static void FAR * ORABIND1;), and define the parameters (

static Lrd_var_desc UID =

{lrd_var_desc_eyecat, 1, lrd_dbtype_oracle, {1, 1, 0},

Dt_sf_stripped_spaces};).

Why do you want to define it here instead of simply using parameterization? Because that will cause a lot of pressure on the press, not conducive to testing. Here's how many variables and how many arguments you use in your script, depending on your foot, and how much you want to define here. Next, modify the script to place a one-time login login in init and end, using the lrd_assign and Lrd_ora8_bind_placeholder commands to override the parameters, such as

Lrd_ora8_stmt (ORASTM6, "Select COUNT (*) as counter from * * * WHERE ***_id="

": U and (status = 0 or"

"Status is null", 1, 0, 0);

Lrd_assign (&uid, "{UID}", "", 0, 0);

Lrd_ora8_bind_placeholder (ORASTM6, &orabind1, "U", &uid, 0, 0, 0);

This way, the script is almost done. Compile, no problem passed the ^o^

Put the script on the control machine, you can start to pressure, note that the database server is measured by the configuration of the parameters to be recorded, so as to modify parameter tuning can be analyzed clearly. The Iops,time,tps and response times of the database are recorded, and the results are summarized in the report.