eG Monitoring
 

Measures reported by TibTranWrkldTest

Knowing the count of transactions executing on the Tibero 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 TibTranWrkldTest 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.

Outputs of the test : One set of results for each database server being monitored.

The measures made by this test are as follows:

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_chgs_count Indicates the number of database blocks that were changed per transaction. Blocks/Trans
Phy_reads Indicates the number of physical reads performed per transaction. Reads/Trans
User_calls Indicates the number of user calls made per transaction. Calls/Trans  
Parses_count 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 Tibero Database. During the parse call, Tibero Database:

  • Checks the statement for syntactic and semantic validity.
  • Determines whether the process issuing the statement has privileges to run it.
  • Allocates a private SQL area for the statement.

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_count 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.
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  
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.
Tot_transactions Indicates the rate at which transactions were executed by the server. Trans/Sec A steady increase in the value of this measure could indicate an increase in the transaction load on the server. A consistent and notable drop in the value of this measure could indicate a bottleneck in transaction processing.