Management Module Resources (Sun Management Center 3.5 Installation and Configuration Guide)

Sun Management Center 3.5 Installation and Configuration Guide

Management Module Resources

The resource requirements of management modules depend on the following factors:

The number of managed properties in the module.
The volume of managed property data processed in the module. Tables with many rows of data incur increased resource usage.
The refresh intervals of managed properties.
The complexity of data collection and rule processing.

The following table summarizes the resource impact of the Sun Management Center management modules.

Table C–3 Sun Management Center Management Module System Impact Summary


Module	Impact
Agent Statistics	Incurs low footprint increase and low CPU load increase.
Config-Reader	Uses CPU and memory relative to the complexity of the hardware configuration of the managed node.
Data Logging Registry	Incurs low footprint and CPU load increase that is proportional to the amount of data values being logged.
Directory Size Monitoring	Incurs a low footprint increase that is proportional to the number of directories monitored. Incurs low to moderate CPU load that depends on both the number of directories monitored and the activity within those directories.
Dynamic Reconfiguration	Has minimal footprint impact and utilizes CPU only when performing reconfiguration operations.
File Monitoring	Incurs low footprint increase proportional to the number of files that are monitored. Incurs low to moderate CPU load, depending on both the number of files that are monitored and the activity within those files.
File Scanning (System Log)	Incurs low footprint and CPU load increase.
Health Monitoring	Has relatively low impact on resources.
HP JetDirect	Incurs low footprint increase and low CPU load.
IPV6 Instrumentation Module	Incurs low CPU load increase and low to medium footprint increase dependent on the number of network interfaces.
Kernel Reader, Full	Affects CPU and memory based on the number of file systems, CPUs, and other system resources under management, as well as the rate of refresh of this information. Consumes more resources than the Simple Kernel Reader.
Kernel Reader, Simple	Has minimal impact on CPU and memory.
MIB-II Instrumentation	Incurs minimal CPU load and low to moderate footprint increase depending on the number of network interfaces, and the size of the routing tables, ARP tables, and related system tables.
MIB-II Proxy Monitoring	Incurs moderate footprint increase proportional to the size of the MIB of the proxy-monitored SNMP agent. Incurs low to moderate CPU load proportional to the number of managed objects in the proxy-monitored SNMP agent.
MIB-II Simple	Incurs virtually no CPU load and very little footprint increase, proportional to the size of the system interfaces, IP forwarding, and IP address table.
NFS File System	Incurs low footprint increase that is proportional to the number of network file systems mounted on the host machine, and low CPU load.
NFS Statistics	Incurs low footprint increase and low to moderate CPU load.
Print Spooler	Incurs low footprint and CPU load increase.
Solaris Process Monitoring	Incurs low footprint increase that is proportional to the number of processes monitored. Incurs low to moderate CPU load, depending both on the number of processes monitored and how often the processes are started and stopped.
Sun StorEdge A5x00 Array, Sun StorEdge T3 Array	Incurs moderate footprint and load increase that is proportional to the size of the storage device.