Oracle Transaction Workload Test
Knowing the count of transactions executing on the Oracle database server per second can indicate the transaction load on the server. However, the true impact of this load can be assessed and understood only if administrators are enabled to determine the number and type of database operations each transaction triggers. This is where the Oracle Transaction Workload test helps! This test reports how many key database operations - eg., data modifications, block changes, reads/writes, parses, rollbacks, etc. - are performed on the server per transaction. This way, the test reveals the real workload of the server. In addition, the test also enables administrators to compare current CPU usage with the real workload, so that they can figure out whether/not the server needs to be resized to handle its load.
Target of the test : An Oracle server
Agent deploying the test : An internal agent
Outputs of the test : One set of results for every SID monitored.
|
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Redo size: |
Indicates the amount of data written to the redo logs per transaction since the last measurement period. |
MB/Trans |
If the value of this measure keeps growing, it could indicate that transactions are making numerous and frequent changes to the data in the databases. |
Logical reads: |
Indicates the number of logical reads performed by the server per transaction. |
Reads/Trans |
These measures are good indicators of the level of activity that every transaction generated on the database server. |
Block changes: |
Indicates the number of database blocks that were changed per transaction. |
Blocks/Trans |
|
Physical reads: |
Indicates the number of physical reads performed per transaction. |
Reads/Trans |
|
Physical writes: |
Indicates the number of physical writes performed per transaction. |
Writes/Trans |
|
User calls: |
Indicates the number of user calls made per transaction. |
Calls/Trans |
|
Parses: |
Indicates the number of parses executed by the server per transaction. |
Parses/Trans |
Parsing is one stage in the processing of a SQL statement. When an application issues a SQL statement, the application makes a parse call to Oracle Database. During the parse call, Oracle Database:
If the value of this measure keeps increasing consistently, it could indicate on an average, transactions are executing many SQL statements on the server, thus generating more parses. |
Hard parses: |
Indicates the number of hard parses executed per transaction. |
Parses/Trans |
As opposed to a soft parse, a hard parse loads the SQL source code into RAM for parsing. A high value for this measure therefore indicates that the server is performing many hard parses. |
WA memory processed: |
Indicates the amount of work area memory used up by the server per transaction. |
MB/Trans |
Oracle Database reads and writes information in the PGA on behalf of the server process. An example of such information is the run-time area of a cursor. Each time a cursor is executed, a new run-time area is created for that cursor in the PGA memory region of the server process executing that cursor. For complex queries (such as decision support queries), a big portion of the run-time area is dedicated to work areas allocated by memory intensive operators, including:
For example, a sort operator uses a work area (sometimes called the sort area) to perform the in-memory sort of a set of rows. Similarly, a hash-join operator uses a work area (also called the hash area) to build a hash table from its left input. If the amount of data to be processed by these two operators does not fit into a work area, then the input data is divided into smaller pieces. This allows some data pieces to be processed in memory while the rest are spilled to temporary disk storage to be processed later. A consistent increase in the value of this measure is indicative of excessive usage of the work area by transactions. This could indicate that the transaction workload is characterized by complex queries that use memory intensive operators such as sort, hash-join, etc. You may want to fine-tune the work area size in order to enable it to handle the memory-intensive load better. |
Logons: |
Indicates the number of users logging in per transaction. |
Logons/Trans |
A steady rise in this value is indicative of a steady increase in user activity on the server. |
Executes: |
Indicates the number of executes performed per transaction. |
Executions/Trans |
|
Rollbacks: |
Indicates the number of rollbacks performed per transaction. |
Rollbacks/Trans |
Ideally, the value of this measure should be low. This is because, rollbacks are expensive operations and should be avoided at all costs. A consistent increase in the value of this measure is hence a cause for concern. |