Virtualization

In a virtual environment, you can share resources to maximize your return on hardware investment. However, sp reacts to network conditions in real time. As a result, the product requires CPU resources, memory resources, and disk speeds to be running at optimal capacity. If any one of these resources is affected because of another virtual machine, sp performance is affected. Therefore, we recommend running sp with CPU and memory resources that are dedicated 100 percent of the time. If you are using a storage area network, use the performance requirements that we recommend in the Hardware section.
casp941
In a virtual environment, you can share resources to maximize your return on hardware investment. However,
reacts to network conditions in real time. As a result, the product requires CPU resources, memory resources, and disk speeds to be running at optimal capacity. If any one of these resources is affected because of another virtual machine,
performance is affected. Therefore, we recommend running
with CPU and memory resources that are dedicated 100 percent of the time. If you are using a storage area network, use the performance requirements that we recommend in the Hardware section.
Do not run VMware VMotion on virtual machines (VMs) that are running
because
always requires dedicated resources. However, if you stop all
processes on VMs, you can run VMware VMotion on those VMs.
As a best practice for virtual machines that are used for
, dedicate system resources as specified in the Hardware section. For VMware environments, consider the following points:
  • Ensure that required resources are always available (reserved). Assign dedicated resource groups to the
    virtual machines regardless of the state of other VMs that are running on the same server. Make resource group allocations according to the sizing information from the
    Sizing Tool and the recommendations in this document.
  • Create specific RAID volumes or LUN with dedicated disks/spindles to the
    system. These volumes help to avoid disk I/O contention with other applications that share the same RAID or storage array. Allocate large volumes of disks/spindles to the RAID volume or LUN. Larger volumes enable a greater I/O distribution and maximum read/write times for the
    processes.
  • The VMware administrator can reserve memory and CPU resources within Clusters or Resources Pools, rather than making reservations on individual VMs.
  • On the
    SpectroSERVER
    hosts, lower CPU percent ready times were observed with two vCPUs than with four vCPUs. More vCPUs are not always better.
  • Disk access times of more than 10 (ms) noticeably affected performance on a
    SpectroSERVER
    with a significant load.
  • Do not allow the VM snapshots to continue for long periods of time. The delta implementation of snapshots can affect the
    SpectroSERVER
    performance.
  • The VM HBA assignments can also affect
    SpectroSERVER
    performance.
Basic Configuration for VMware
Set the following values from the Hardware tab on the Edit Settings dialog:
  • 2 vCPUs
  • Configured memory: 8 GB (The guest operating system assumes this value as the available physical memory)
Additional Configuration for VMware
If a VM contention affects the ESX server, set the following values from the Resources tab on the Edit Settings dialog:
  • Memory
    • Shares: High
    • Reservation: 2-4 GB (hardware-dependent; use with care)
    • Limit: Unlimited
  • CPU
    • Shares: High
    • Reservation: 0 ((hardware-dependent; use with care)
    • Limit: Unlimited