HP 9000 Containers A.03.01 on HP Integrity Server Administrator Guide HP-UX 11i v3 (5900-3112, June 2013)

• The CPU requirements vary with the workload characteristics. Workloads that have a higher
requirement inside HP 9000 containers are the following:
◦ Applications that spawn several short lived processes or threads.
◦ Applications that concurrently run several CPU bound processes.
◦ Script intensive applications.
◦ Java based applications.
◦ Applications that have intensive floating points.
◦ Applications that load and unload several libraries dynamically.
• A guideline, assuming the target server uses Intel Itanium Processor 9350 cores, is to start
with an approximate 1:<frequency in GHz on HP 9000 server> core ratio. For example, if
the HP 9000 server is using 1 GHz PA-RISC cores, use 1:1ratio for sizing. The core sizing
can be up to 25% lesser with Intel Itanium Processor 9560.
NOTE: The guidelines are common case estimates and some changes might be needed based
on the results of Proof-of-Concept testing.
1.7 Resource entitlement
HP-UX Containers supports the feature to allocate CPU and memory usage per container. By default,
a PRM group is allocated to each container on the system. CPU and memory allocation can be
assigned to each PRM group. The PRM group provides two allocation models for CPU cores:
• Share based allocation—Restrictions (excluding maximum utilization caps) are not applied
until the managed resource is fully utilized, at which point the operating system scheduler or
memory manager applies an algorithm to allocate resources proportional to the share size of
each PRM group. This model ensures that individual containers can utilize available resources
without frequent tuning of allocations.
• Dedicated allocation—The specified PRM group is allocated a fixed quantity of resource for
its own exclusive use. This model guarantees immediate and complete access to the resource
at the expense of the ability to allow other PRM groups access to the currently unused resource.
Dedicated CPU allocation is used to limit the software license requirements for some software
products.
You can apply a combination of resource allocation models on a single server. You can also
disable PRM, either to use a different resource allocation utility such as WLM or gWLM, or to
disable resource management per container.
For more information about PRM and WLM, see the documents related to PRM and WLM at http://
www.hp.com/go/hpux-core-docs.
1.8 Using ARIES without HP 9000 Containers
You can use stand-alone ARIES emulator to run applications compiled for PA-RISC. The transition
involves copying the application-related files from HP 9000 server to HP Integrity system. ARIES
is supported with other HP virtualization solutions (such as HP Integrity VM, HP-UX vPars, and
HP-UX nPars) and with HP-UX system and workload native containers.
Table 3 (page 13) lists a comparison of transition using stand-alone ARIES and HP 9000 Containers.
12 Introduction