IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Manage historical data
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Performance impact of historical data requests
The impact of historical data collection and warehousing on Tivoli Management Services components is dependent on multiple factors, including collection interval, frequency of roll-off to the data warehouse, number and size of historical tables collected, system size, and more.
- Impact of large amounts of historical data on the monitoring server or agent
The default location for storing short-term historical data is at the monitoring agent, although in certain configurations the monitoring server might be preferable.
- 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.
- Scheduling the warehousing of historical data
The same issues with requesting large rowsets for historical reports apply to scheduling the warehousing of historical data only once a day. The more data being collected and stored, the more resources required to read data into memory and to transmit to the data warehouse. If possible, make the warehousing rowset smaller by spreading the warehousing load over each hour, that is, by setting the warehousing interval to one per hour, rather than one day.
- Use a data mart to improve long or complex queries
This section describes the how a data mart can be used to increase the performance of your primary datastore.
Parent topic:
Manage historical data