- This article explains how to troubleshoot performance issues.
- Tivoli Storage Manager KM for PATROL
Tivoli Storage Manager KM: Troubleshooting Performance Issues
KB1147 - Jun 26, 2014
The Tivoli Storage Manager KM for PATROL may have deep impact on resources and more especially on:
- The CPU and Memory Usage
- The Network Traffic
Troubleshooting CPU and Memory Usage
The CPU and memory usage strongly depends on the size and complexity of your environment and on the KM configuration. The more complex the environment, the more memory will be needed. As an example, a PATROL Agent consumes between 5MBytes and 10MBytes of additional system memory when monitoring a standard installation of Tivoli Storage Manager with the TSM KM; which is not negligible. The impact of the TSM KM on the memory usage can however be reduced by:
- disabling the monitoring of unnecessary component instances (by using the Configuration menu)
- disabling unwanted components (by setting their instance limits to 0)
- disabling unwanted collectors (by using the PATROL Configuration Manager)
- increasing the collector scheduling interval (by using the PATROL Configuration Manager)
- decreasing the instance limits to limit the number of instances created by the collectors
The data collectors in TSM KM use the Tivoli Storage Manager command line interface to obtain Tivoli Storage Manager information. Most of the performance degradation is associated with these command executions and with the amount of data returned. Overall performance may be improved by following the regular housekeeping on all Tivoli Storage Manager systems.
Troubleshooting Network Traffic Issues
The network traffic will depend on the number of PATROL Consoles that are connected to the PATROL Agent and the data collection frequency. Under normal conditions, the TSM KM generates minimal network traffic. Most of the data is kept on the managed node.