In order to increase the default scale limits for vVols, Everpure needed to make sure that we could support high values of concurrent requests and the scale of 2000 vVol VMs. For these tests the following was being tested.
- One FlashArray X70 for the test connected to 4 vCenter Servers
- Two vCenter Servers are running 7.0 U2a and two vCenter Servers are running 6.7 U3 p03
- Each vCenter had 500 vms deployed to them, powered on, etc.
- Each VM has 3 virtual disks, vmdk1 is 350 GB, vmdk2 is 1 TB and vmdk3 is 1TB.
- Leading to 5 vVols per VM (Config + 3 Data + 1 Swap)
Here are some quick numbers for the total times and average task times for these tests.
|
Tests at 50k IOPs and ~30% Load |
Purity 6.1.7 2000 VM Test Time |
|
Cloning 2000 VMs from a single template in batches of 100 |
1 hour 20 minutes (1:24 average task time) |
|
Powering on 2000 VMs in batches of 100 |
55 minutes (1:20 average task time) |
|
Taking Managed Snapshots of 2000 VMs in batches of 100 |
30 minutes (0:55 average task time) |
|
Destroying Managed Snapshots of 2000 VMs in batches of 100 |
16 minutes (0:30 average task time) |
|
Powering off 2000 VMs in batches of 100 |
17 minutes (0:28 average task time) |
|
Destroying 2000 VMs in batches of 100 |
30 minutes (0:50 average task time) |
The main thing to take away from these numbers is that the average task times are all exceeding expected times and the total workflow times for operations for 2000 VMs looked good. As we increased the load on the FlashArray, we wanted to make sure that there weren't failed operations and the average task times were still within a reasonable variance.