Database performance recommendations

TrueSight Middleware and Transaction Monitor (TMTM) behaves much more like an OLTP system than a DSS/OLAP system, but qualifies as a mixed workload because there are elements of both.

The end user experience of the TMTM Monitor Console is directly impacted by the responsiveness of the database. The database cache should be large enough to accommodate very efficient access to the so called reference tables, which are tables that are updated infrequently by read from very frequently. Non-reference tables are tables that are used to store data such as Performance and Availability history data, Transaction Management history data as well as journal data. These tables are updated frequently, in some cases constantly.

The nonreference tables must be provisioned with enough database system resources to efficiently handle a process that is initiated by TMTM called History compression. This process runs for both for Performance and Availability data and for Transaction Management data.

As the size of the reference tables and the requirement for history compression are different for every installation, so are the memory demands. In many cases, the database workload might demand a large cache. For DB2, tune the factors that influence buffer pool hit ratio. For Oracle and MS SQL Server, tune the factors that influence the buffer cache hit ratio.


TMTM uses index optimized statements that use database memory very efficiently. A low hit ratio (< 95%) suggests excessive disk activity. 

See the following sections for specific performance recommendations for the supported DBMS types:

Was this page helpful? Yes No Submitting... Thank you