Article ID: 113433, created on Mar 7, 2012, last review on Aug 12, 2014

  • Applies to:
  • Virtuozzo
  • Virtuozzo containers for Linux
  • Virtuozzo hypervisor
  • Virtuozzo hypervisor


There are four key objectives for success with VPS hosting:
Pursue Operational Excellence Optimize Density

This article describes technical recommendations for using Parallels Virtuozzo Containers as a virtualization platform for IaaS and recommendations for achieving optimal density and operational excellence with this product.

Operational recommendations

  • Disk recommendations
    1. Use fast HDDs in RAID 10 array, e.g., 4x500GB HDDs.
    2. Allocate swap relative to amount of RAM.
      RAM swap
      0 - 4 GB 2 GB
      4 - 16 GB 4 GB
      16 - 64 GB 8 GB
      64 - 256 GB 16 GB
      256 - 512 GB 32 GB
    3. Use hotplug-compatible disk bays and RAID controllers.
    4. Avoid using fans on controllers.
    5. Use battery backup controllers.
  • Environment recommendations
    1. Use compatible native environment on the host, i.e., RHEL 6.x or CentOS 6.x for Parallels Virtuozzo Containers for Linux 4.7.
    2. Be consistent with HW on nodes to reduce risk of driver-related problems.
    3. Do not use 3rd-party drivers on nodes.
    4. Keep configurations synchronized across all the Parallels Virtuozzo Containers servers.
    5. Test new hardware before production switch-over.
  • Deployment recommendations
    1. Use Parallels Server Bare Metal to streamline deployment.
    2. Use PXE boot to automate network-based installation.

Density recommendations

  • Workload recommendations
    Match the server to the business model.
    Workload CPU Memory Containers
    Web Applications\Parallels Plesk Panel 2x Quad-Core 64 GB 80-100
    Database\Compute Intensive 2x Eight-Core 128 GB 80-100

  • Resources management recommendations
    1. CPU: Ensure that CPU core mumbers and limits are set according to your hardware environment.
    2. Disk I\O: Prevent situations where high disk I/O activities in one Container will slow down the performance of other Containers.
    3. Disk I\O: Set the limit to 75% max disk throughput.
    4. vSwap: Limit the maximum amount of allocated memory by specifying the amount of physical memory and virtual swap space that can be used by a Container.

a26b38f94253cdfbf1028d72cf3a498b a26b38f94253cdfbf1028d72cf3a498b e8e50b42231236b82df27684e7ec0beb d02f9caf3e11b191a38179103495106f 0dd5b9380c7d4884d77587f3eb0fa8ef 2897d76d56d2010f4e3a28f864d69223 6311ae17c1ee52b36e68aaf4ad066387

Email subscription for changes to this article
Save as PDF