Maximizing performance of multi-node workloads can be challenging. Should I maximize CPU clock rate, or RAM size per node, or network
bandwidth? And how do I analyze performance of each component while also measuring aggregate throughput?
Solaris Zones provide characteristics that are useful for multi-node architectures:
- Architectural flexibility: easily remove a network bottleneck between two components by running both in zones on one Solaris
server - and move any of them to different servers later as processing needs change
- Convenient, dynamic resource management, assign a workload to a set of CPUs for predictable, consistent performance, ensure
that each workload component has access to sufficient hardware resources, etc.
These characteristics are displayed in the world record benchmark result for Oracle JD Edwards EnterpriseOne. It was achieved using
Solaris Containers (Zones) to isolate individual software components, including the WebLogic-based applications and Web Tier Utilities.
Solaris Zones features enabled software isolation and resource management, making the process of fine-tuning resource assignment very easy.
For more details, see: