CPU Resources

Sun Management Center agents add a minimal computational load on the host system. The computational load is caused by normal management operations, including periodic data acquisition, alarm rule processing, alarm annunciation, alarm action execution, and the processing of client requests.

The amount of load introduced is proportional to the rate at which data is gathered, the amount of data gathered, the number of alarms detected, and the number of user requests. The percentage of CPU resources consumed therefore depends on the number and type of modules loaded on the system, the configuration of these modules, and the computational capacity of the host system.

Even on low-end machines with a comprehensive suite of modules loaded and high management activity, the agent should never consume more than a fraction of the CPU resources.

Light configurations are based on an agent with the following modules loaded:

• Agent Statistics

• Kernel Reader (Simple)

• MIB-II System (Simple)

The following tables give estimates of the agent CPU and RAM usage for light modules.

Table C–1 Agent CPU and RAM Use Estimates for SPARC (light modules)

Machine	Memory (MB)			CPU (%)			Resident Set Size (MB)			Virtual Memory (MB)
	Min	Avg	Max	Min	Avg	Max	Min	Avg	Max	Min	Avg	Max
Small	0.4	0.4	0.4	0.3	0.3	0.3	7.46	7.46	7.46	9.17	9.17	9.17
Medium	0.2	0.2	0.2	< 0.1	< 0.1	< 0.1	7.38	7.43	7.43	9.12	9.17	9.17
Large	0.1	0.1	0.1	< 0.1	< 0.1	< 0.1	7.62	7.68	7.68	9.34	9.40	9.40
Extra Large	0.1	0.1	0.1	< 0.1	< 0.1	< 0.1	7.82	8.08	8.12	9.40	9.59	9.62
CMT (T2000)	0.1	0.1	0.1	< 0.1	< 0.1	< 0.1	8.44	8.44	8.44	9.43	9.43	9.43

Table C–2 Agent CPU and RAM Use Estimates for x86 (light modules)

Machine	Memory (MB)			CPU (%)			Resident Set Size (MB)			Virtual Memory (MB)
	Min	Avg	Max	Min	Avg	Max	Min	Avg	Max	Min	Avg	Max
Small	0.6	0.6	0.6	< 0.1	< 0.1	< 0.1	6.10	6.21	6.22	7.69	7.76	7.76
Medium	0.2	0.2	0.2	< 0.1	< 0.1	< 0.1	6.25	6.25	6.25	7.80	7.80	7.80
Large	0.2	0.2	0.2	< 0.1	< 0.1	< 0.1	6.19	6.29	6.29	7.76	7.82	7.82

Heavy configuration is based on an agent with the following modules loaded:

Agent Statistics Data Logging Registry Health Monitor Kernel Reader (Full) MIB-II Instrumentation MIB-II Proxy Monitoring Solaris Process Details

Config Reader Directory Size Monitoring File Scanning Script Launcher Script Repository Service Management Facility

The heavy configuration is likely to be greater than needed. Larger machines typically have larger hardware configurations with more processors and disks. These configurations result in greater memory consumption by agents running on larger machines. Heavy modules can include various user-defined custom modules.

The following tables give estimates of the agent CPU and RAM usage by system type for heavy modules.

Table C–3 Agent CPU and RAM Use Estimates for SPARC (heavy modules)

Machine	Memory (MB)			CPU (%)			Resident Set Size (MB)			Virtual Memory (MB)
	Min	Avg	Max	Min	Avg	Max	Min	Avg	Max	Min	Avg	Max
Small	1.0	1.0	1.0	1.2	1.24	1.4	19.15	19.15	19.15	21.68	21.68	21.68
Medium	0.5	0.5	0.6	< 0.1	0.66	1.3	20.93	20.95	20.96	23.60	23.61	23.61
Large	0.2	0.2	0.2	0.1	0.12	0.2	19.13	19.16	19.20	21.88	21.88	21.88
Extra Large	0.1	0.1	0.1	0.1	0.1	0.1	23.97	23.99	24.00	26.38	26.38	26.38
CMT (T2000)	0.3	0.35	0.4	0.1	0.19	0.3	22.42	24.41	26.53	23.69	25.74	27.79

Table C–4 Agent CPU and RAM Use Estimates for x86 (heavy modules)

Machine	Memory (MB)			CPU (%)			Resident Set Size (MB)			Virtual Memory (MB)
	Min	Avg	Max	Min	Avg	Max	Min	Avg	Max	Min	Avg	Max
Small	1.3	1.4	1.4	0.1	0.1	0.1	13.40	13.76	13.79	16.60	16.96	17.00
Medium	0.4	0.4	0.4	0.1	0.2	0.3	14.25	14.43	14.45	17.33	17.50	17.52
Large	0.4	0.4	0.4	< 0.1	0.06	0.1	13.97	14.81	14.89	17.00	17.82	17.90