N1 AA Analyzer: Server Group Utilization

This section gives a detailed explanation of both MDX queries:

• CPU - Server group utilization

• MEM - Server group utilization

Based on the measured CPU/Memory utilization, the total host utilization within the specified timeframe is displayed and qualified. For example, low, good, or high host utilization. The qualification is based on customizable threshold values %cpulow and %cpuhigh.

Figure A–1 Example of CPU Utilization

Looking at the host CPU utilization of netra1 in the specified time frame:

• Avg util: The average utilization was low, because the measured average of 11.5%, see column Avg%, is less than the threshold of 30% (the value of %cpulow).

• Peak util: There have been only some utilization peaks. That means less than 5% (the value of %cpupeakslower) of all measured values are greater than the threshold of 75% (the value of %cpuhigh).

• Avg % = The average utilization was 11.5%.

• Max % = The maximal utilization was 37.4%.

• Low # = 88 values were less than the threshold of 30% (the value of %cpulow).

• Good # = 8 values are in between 30% and 75% (the value of %cpulow and %cpuhigh).

• High # = 0 values are greater than the threshold of 75% (the value of %cpuhigh).

• Used = 9,923 CPU seconds have been utilized. (Absolute number of used CPU seconds).

• Free = 76,477 CPU seconds have been free. (Absolute number of unused CPU seconds).

• Total = 86,400 CPU seconds have been available. (Absolute number of available CPU seconds = Used + Free).

Figure A–2 Example of Memory Utilization

Looking at the host memory utilization of netra1 in the specified timeframe:

• Avg util: The average utilization was high, because the measured average of 294.3% (see column Avg%) is greater than the threshold of 75% (the value of %memhigh).

• Peak util: There have been many utilization peaks. That means more than 10% (the value of %mempeaksupper) of all measured values are greater than the threshold of 75% (the value of %memhigh).

• Avg % = The average utilization was 294.3%.

• Max % = The maximal utilization was 301.9%.

• Low # = 0 values are less than the threshold of 30% (the value of %memlow).

• Good # = 0 values (of all measured values) are in between 30% and 75% (the value of %memlow and %memhigh).

• High # = 96 values (of all measured values) are greater than the threshold of 75% (the value of %memhigh).

• Used 0 = On average 987,382,016 bytes have been allocated.

• Free 0 = On average –651,837,696 bytes have been free. A negative value indicates that more memory was allocated from the applications than was available as RAM.

• Total 0 = On average 335,544,320 bytes have been available memory as RAM (the total of Used + Free).

The parameters mentioned previously are maintained in N1 AA Analyzer customizing. See Basic Setup. The following table summarizes all available parameters within both MDX queries.

All the parameters given in the table below can be used for server group spanning or server group specific parameterisation.

• The parameter none.analyzer.constants.XY is mandatory and server group spanning valid.

• The parameter servergroup.analyzer.constants.XY is optional and server group specific valid. It overwrites the parameter none.analyzer.constants.XY within this specific server group.