HP PMP Data Differs from Utilization Provider Data

Differences in Memory Data

Capacity Advisor normally measures memory collected from the Utilization Provider, which returns the sum of memory allocated to the processes on the system.

HP PMP collection provides the total memory less the zeroed, free, and standby memory.

This means that HP PMP counts memory used by the operating system, whereas the Utilization Provider does not. The memory use reported by HP PMP is about 20% higher than memory use reported by the Utilization Provider.

Because Capacity Advisor assumes a different memory amount than HP PMP provides, Capacity Advisor may overestimate the memory needed when using HP PMP data to analyze stacking several application instances in a system running a single instance of an operating system.

While either the Utilization Provider data or the HP PMP data can be used to plan memory size in a new configuration, you should not use a mix of HP PMP and Utilization Provider data when looking for a trend in memory utilization.

Differences in Network Data

HP PMP does not report the correct network IO when network interface cards (NICs) are being teamed for network fault tolerance (for example, by using HP Network Config utility).

That is, for a system with 2 NICs teamed as one single logical NIC, Utilization Provider reports the addition of TX and RX Mbps for the teamed NIC.

HP PMP adds the metrics from the 2 NICS, ignoring that they are working as a teamed NIC.

For a teamed configuration, the HP PMP network utilization curve will be always twice that of the Utilization Provider data.

If you know you have teamed NICs, or if you suspect your imported network data is twice as high as it should be, you will want to instruct Capacity Advisor to ignore the imported data. When logged in as a user authorized to use the Capacity Advisor toolbox on the CMS, you will be able to mark data as invalid. You can do this from the Profile Viewer, or by using the capprofile(1M) command.