Technical data

Virtual Partitions (vPars) Management on nPartitions
Introduction to Managing vPars on nPartitions
HP System Partitions Guide: Administration for nPartitions, rev 5.1 446
You can load and run a vPars-enabled HP-UX 11i kernel in both vPar
environments and non-vPars environments. You do not need to
reconfigure a vPars-enabled kernel for non-vPars use.
nPartition and
vPars Performance
In general in HP Superdome Virtual Partitions environments, HP-UX
11i and application performance is nearly equivalent to the performance
given by a non-vPars nPartition that has the same hardware and
software resources and configuration.
Also see the document HP-UX Virtual Partitions Ordering and
Configuration Guide for more vPars performance info.
The main performance factor for vPars running in nPartitions is the
underlying nPartition’s hardware configuration: the cells and
corresponding processors, memory, and I/O assigned to and actively used
in the nPartition.
As in non-vPars nPartition environments, all memory is interleaved
across all active cells in the nPartition when Virtual Partitions are
running in an nPartition. Also on all HP nPartition servers, each
processor has its own runway bus for communication to memory and I/O.
As a result, the locations (hardware paths) of processors assigned to a
Virtual Partition do not affect performance. In general all processors
have the same memory latency when accessing any significant amount of
memory in an nPartition.
The rest of this chapter covers requirements, guidelines, procedures, and
tools for using vPars on HP Superdome servers.