Reference database objects
Reference database objects are tables and related objects that TrueSight Middleware and Transaction Monitor reads from very frequently and can affect overall product performance. The volume of these objects has a direct relationship to the amount of database memory that must be available to achieve optimal performance.
For large installations, segregate the reference tables from other tables. The database cache hit ratio for these reference tables should trend towards 100%. The reference tables (and their associated indices) that are candidates to isolate into a separate pool are listed in the table below.
Table name | Performance impact |
|---|---|
qp_artif_attrs | medium |
qp_attr_types | medium |
qp_event_inputs | high |
qp_event_rules | high |
qp_event_templates | medium |
qp_hdtmpl_oid_asso | high |
qp_hdtmpllrrules | low |
qp_nodes | critical |
qp_obj_info | critical |
qp_typedefs | high |
Consult your DBMS vendor documentation for instructions on how to assign objects to buffer pools (DB2) or how to assign objects to the keep pool (Oracle).
It is very important that statistics for the reference tables and indexes be kept current. These database objects must be kept in a well-organized state.
Comments
Log in or register to comment.