IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Manage historical data > Performance impact of historical data requests
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Requests for historical data from large tables
Requests for historical data from tables that collect a large amount of data have a negative impact on the performance of the Tivoli Management Services components involved. To reduce the performance impact on your system, set a longer collection interval or create a filter (or both) for tables that collect a large amount of data.
For optimal performance, best practice is to ensure the short term history file does not exceed 1 GB.
You specify the collection interval and filter criteria in the History Collection Configuration window. To find out the disk space requirements for tables in the IBM Tivoli Monitoring product, see the specific agent's documentation.
While displaying a query-based view, you can set the Time Span interval to obtain data from previous samplings. Selecting a long time span interval for the report time span adds to the amount of data being processed, and might have a negative impact on performance. The program must dedicate more memory and CPU cycles to process a large volume of report data. In this instance, specify a shorter time span setting, especially for tables that collect a large amount of data.
If a report rowset is too large, the report request can drop the task and return to the Tivoli Enterprise Portal with no rows because the agent took too long to process the request. However, the agent continues to process the report data to completion, and remains blocked, even though the report data is not viewable.
There can also be cases where the historical report data from the z/OS Persistent Data Store might not be available. This can occur because the Persistent Data Store might be not be available while its maintenance job is running.
Parent topic:
Performance impact of historical data requests