IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Performance tuning
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Tivoli Enterprise Portal Server
The Tivoli Enterprise Portal Server (portal server) acts as a conduit for Tivoli Enterprise Portal clients requesting data for analysis from monitoring agents and other components within the enterprise. The portal server connects directly to the hub monitoring server, which it queries for enterprise information and receiving updates as they occur. As it is responsible for handling large amounts of data, it can be a potential bottleneck within the IBM Tivoli Monitoring environment. This section outlines considerations to optimize the portal server performance.
The portal server database stores information related to the presentation of monitored data at the portal client, including definitions related to users, workspaces and views. After IBM Tivoli Monitoring V6.1 Fix Pack 3, the portal server also stores information related to events and event attachments in the portal server database. Before IBM Tivoli Monitoring V6.1 Fix Pack 3, the portal server database required little or no tuning. In environments with a moderate to high rate of events, the portal server database might require some tuning to optimize performance. In particular, the KFWTSIT table, which is used to store events, can grow large.
If you are using DB2 for the portal server database, consider the following tuning recommendations:
- Manual control of the DB2 bufferpool size for the TEPS database is recommended over letting DB2 self-tune the bufferpool size. If DB2 is configured to do self-tuning of the bufferpool size, the size chosen is often much larger than necessary for good Tivoli Enterprise Portal Server performance. A bufferpool size of 10,000 4K pages (about 40 MB) should be sufficient for most environments. The default buffer pool size is 250 4K pages. Increase the size of this buffer pool to minimize disk I/O activity.
- The following commands illustrate how to increase the size of the buffer pool to 10000 4K pages (from a DB2 command prompt):
Because the KFWTSIT table is the most active table, use the runstats and reorg facilities on a regular (for example, daily) basis.
The following commands illustrate how to run the RUNSTATS facility on the KFWTSIT table (from a DB2 command prompt):
The following commands illustrate how to run the REORG facility on the KFWTSIT table (from a DB2 command prompt):
These tuning changes can also be made using the DB2 Control Center.
- Portal server parameter tuning
This section provides some information about parameters you might consider editing to improve portal server performance.
- For environments with more than 10 events per minute, consider disabling the Event Assistant
The Event Assistant creates multiple tables within the Tivoli Enterprise Portal Server database, and processing overhead by the Event Assistant increases the Tivoli Enterprise Portal Server CPU, disk, and memory usage. The Event Assistant is enabled by default.
- Perform periodic table maintenance for Tivoli Enterprise Portal Server DB2 database tables
If you are using DB2 as the Tivoli Enterprise Portal Server database, you should perform periodic table maintenance on the Tivoli Enterprise Portal Server tables, including RUNSTATS.
Parent topic:
Performance tuning