Using SAP with HP Virtualization and Partitioning

Figure 4. ”Sweet spots” for production systems
With these comparisons in mind, we discuss the various options to deploy production systems:
• “Production, no isolation required” represents for multiple production systems that can share one
OS. Check the previous chapter “to partition or not to partition”. If you don’t find a good reason to
partition among your production systems, this is the sweet spot for your production systems. If you
find a reason to partition, go to the next bullet.
• “Medium/Large production, isolation required” refers to systems that cannot be run on one OS for
some reason. Virtual partitions (vPars) are fine for systems that don’t require complete hardware
isolation; nPars are the technology of choice if complete isolation is required. However if your
systems are very small, please consider the following.
• “Small production, isolation required” applies to systems that cannot be run on one OS, but for
which vPars or nPars are a waste of resources, and which don’t need HW separation. Typically
these are systems ranging from fractions of a processor core in resource consumption, up to about
2 cores. For these systems, Integrity VM provides several benefits:
o automatic resource sharing optimizes resource usage
o ability to allocate fractions of a processor core to a system prevents waste of
resources, using vPars or nPars in these cases will use many more processors in total
o IO device sharing prevents an excessive count of adapters that would come with
implementing a vPar or nPar for every single small system