This is Part 4 of the Jetstress performance testing on Nutanix Acropolis Hypervisor (AHV) series of videos.

This video shows the following:

1. Jetstress performance on the forth node in the cluster after the VM has already been migrated in quick succession from its original node too a 2nd and 3rd node both of which have ran a Jetstress test.
2. Nutanix Controller VM (CVM) CPU utilization

This test is the forth of several test to show the impact to performance by migrating VMs around several nodes in the same cluster which results in not all data being accessible/stored locally.

These post migration tests are designed to show the worst case performance when business critical workloads with large data sets (such as Exchange) move around nodes within a Nutanix AHV cluster. By running Jetstress on multiple nodes in quick succession, the workload on the Nutanix Controller VMs (CVMs) to localize data and maintain a even balance of data across all drives (SSD/HDD) and nodes within the cluster is higher than normal.

While migrating business critical applications around multiple nodes in quick succession (especially while running intensive benchmarks at much higher IOPS that the real world requires) is not something that will occur (unless initiated by an administrator), it demonstrates the performance impact (or lack thereof) of even this unrealistic operation.

Note: As with previous videos, This demonstration is not showing the peak performance which can be achieved by Jetstress on Nutanix.

Part 4

Return to the Table of Contents

Related Articles:

• MS Exchange on Nutanix Acropolis Hypervisor (AHV)
  
• MS Exchange on Nutanix now a MS validated ESRP solution
• Peak performance vs Real World – Exchange on Nutanix Acropolis Hypervisor (AHV)
• How to successfully Virtualize MS Exchange
• Deduplication and MS Exchange
• Think HCI is not ideal way to run your mission-critical x86 workloads? Think again!
• Why Nutanix Acropolis hypervisor (AHV) is the next generation hypervisor