Optimizing the DataChannel Hourly Database Loader (LDR)
This information describes the behavior of the DataChannel
Hourly Database Loader (LDR), and provides instructions for configuring
the default or optimized LDR behavior.
Hourly Database Loader (LDR)
Every hour, the DataChannel Hourly Database Loader (LDR) collects metric data from files that are produced by the CME and loads the data into the database. When in the database, the data is available for display in views and reports.
Default behavior
By default, the LDR attempts to refresh (collect and load) all this data every hour over the duration of the LDR period (daily, weekly, or monthly).
Optimized behavior
Optionally, you can change the default LDR behavior to optimized behavior.
Examples
The following examples illustrate the differences between default and optimized behavior.
Configuring default or optimized behavior
You configure the LDR for default or optimized behavior by opening the Tivoli Netcool Performance Manager Topology Editor and editing the configuration parameter AGGREGATION_FIDELITY for each CME.
Guidelines for collector load balancing
You can optimize resource use, maximize throughput, minimize response time, and avoid overload of any single resource by load balancing.