Best Practices for Deploying in a Virtual Environment
The following best practices are applicable when you deploy ActiveSpaces in a virtual environment.
- Disable vMotion
- While migrating processes from one host to another, vMotion stops processes for a certain period. Consequently, you might lose some members, resulting in cluster instability. You might also experience delay in user operations.
- Disable vSnapshot
- While taking a consistent snapshot, vSnapshot briefly stops the processes for a certain amount of time which can negatively impact the performance of ActiveSpaces.
- Pin the Virtual Machines
- By pinning the resources, you can dedicate memory and CPU to an image. This reduces latency and risk of undue delays in ActiveSpaces. Furthermore, pinning helps you assign physical CPU cores and enables you to allocate NUMA aware memory.
- Disable Memory Ballooning
- Memory access speed and large memory allocation are key aspects of ActiveSpaces. Over allocating memory, as done by memory ballooning, hampers the speed and memory access patterns of ActiveSpaces.
- Reserve Memory
- By reserving memory, you ensure that after ActiveSpaces claims the physical pages, the Hypervisor cannot reclaim them with memory ballooning or Virtual Machine File Swapping techniques.
Copyright © Cloud Software Group, Inc. All rights reserved.