If the primary RTEMS goes down and the agent fails over to the secondary RTEMS, the agent should be able to upload historical data through the WPA on the secondary RTEMS. Recommended deployment is to deploy one WPA on each RTEMS. Use multiple WPAs when the number of agents collecting historical data > 1500ģ. Loses the access to the shortterm historical data during failover to a secondary TEMS.ġ. Typically placed on the same LAN segment as the Warehouse database to allow for the best throughput to the database.Ģ. Drastically lowers the number of agents managed by the TEMS. Demands large disk storage, CPU and memory usage of the TEMS. Slow workspace response time for shot-term historical data. All agents write to one file for each attribute groups. much smaller chunk of data warehousing from multiple boxes. Large chunk of data warehousing from one box vs. Performance implications for the data gathering step in large scale environments with several hundred agents connected to one TEMS. Think carefully of the performance impact before choosing TEMS as the collection location. Find out the largest tables that make up the majority of the warehouse data.Ģ. Estimate the disk space required for shortterm historical data on Agent.Ĥ. Estimate the amount of disk space and network throughput required for historical data collection and warehousingģ. Get the ITM Data Warehouse Load Projects spreadsheet from IBM ISM LibraryĢ. Monitor the Warehouse Database for problemsġ. Use the Projects Spreadsheet and keep it up to date as requirements and environment changes Keep the data for ONLY as long as you need it Never summarize high-volume, low repeatability data unless you have use case that demands it.Ĥ.
Adaptive / dynamic thresholding uses only detailed data. Standard TCR reports & ITPA use only hourly and daily summarization. Gather ONLY the data you need from ONLY the systems you need it fromĮxample: 1000 identical Web Servers in a farm only need historical data for performance planning purpose from a few systemsĮxample: filter the history collection for PROCESS with VSIZE>50MB Start with your Use Cases. Consider the use cases for each attribute group when configuring historical collection.Ģ. Predict and control size of historical dataġ. Is the warehouse database at the best performance? Any variable that can be tuned to achieve faster warehousing?ħ. How many agents that each WPA can serve?Ħ. Where is the history data located, TEMA or TEMS? What are the performance impact?ĥ.
What data need to be collected and how they will be used?Ģ. File size of the shortterm history data stored in local file system grows continuously, data were not able to be warehoused fast enough.ġ.
0 kommentar(er)
