HP-UX WBEM nPartition Provider Data Sheet

about the WBEM infrastructure and administration information, see the
WBEM manual or the man pages. For information about Microsoft’s
implementation of the WBEM standard for Windows (WMI), see the
Microsoft Platform SDK/WMI.
 Managed Resource Documentation
For detailed information about nPartitions, refer to HP System Partitions
Guide: Administration for nPartitions.
5. Known Defects And Performance Considerations
 Performance Considerations.
o The retrieval of the static configuration data fetched by the provider
when a new HP_NParRemoteComplex object is created may take a
significant amount of time, ranging from a few seconds to more than a
minute, depending on the network distance from the provider to the
remote complex. This data, however, will only be fetched once and
will remain cached either until the provider is disabled, the CIM server
stopped, or the UpdateComplex method called on the
HP_NParComplex.
o A similar delay may be encountered even for the local complex. The
same set of static configuration data is retrieved and cached for the
local complex. This occurs when the first request for any data from the
local complex occurs. This data, as in the remote case, is fetched once
and remains in effect until the provider is disabled or the CIM server is
stopped.
o While this static configuration data may be as large as 250 KB or
more, only the minimum set of necessary data is cached by the
provider. The long-term caching of this data should not be a memory
usage consideration.
o When it is necessary to request more than a single instance of a class
defined in this schema, it is more efficient to use enumerateInstances
than to use enumerateInstanceNames and then getInstance for each
instances name returned. In some cases, particularly for power/cooling
domains, cells and I/O chassis, the difference may be
significantly more than simply the overhead of the extra WBEM
requests needed for the second approach.
 Known Defects