Archives for August 2016


Battle Royale: View Composer VS Instant-Clones – Deploy

Horizon 7 added Instant-Clones with the ability to clone a full desktop in 4-5 secs. What is the catch? Not really a catch, but no explanation that it takes a bit of time to prep the desktops. For testing purposes, I decided to clone 100 desktops with View Composer and 100 desktops with Instant Clones.

For these tests I used NX 3460-G4, Win 10, 2 vCPU, 2 GB of RAM

Impact of cloning 100 desktops with View Composer


You can see hypervisor IOPS and disk IOPS. The impact is really shown on what is happening on the backend and CPU used to create the desktops. So roughly 16,000 IOPS to create the desktops with Composer.

Impact of cloning 100 desktops with Instant-Clones

You can see an initial bump in IOPS due to the replica that has to be copied without VAAI. The replica also has to get fingerprinted with does take some time. In my testing it took about eight minutes. The reduction in IOPS is amazing. While you still need performance for running the desktops, you don’t have to worry about provisioning destroying your performance. Disk IOPS was ~ only 1200 IOPS at its peak.

Summary VC vs Instant Clone

Deploy 100 Desktops
View Composer: 5 min
Instant Clone: 14 min —– virtual disk digest – 8.22 min
—– Clone 100 desktops 1.4 min

While the overall process took longer the impact is a lot better with Instant-Clones. With hundreds of desktops Instant-Clones is powerful tool to have in your back pocket. Once Instant-Clones gets GPU support I think they will really take off as the default choice. If you have related questions to performance I encourage you to talk to your Nutanix SE and they can get put you in touch with the Solution and Performance Team at Nutanix.

Related Articles

Tale of Two Lines


The Tale Of Two Lines: Instant-Clones on Nutanix

There was a part of me that wanted to hate on Instant Clones that are new in Horizon 7 but the fact is they’re worth the price of admission. Instant-clones has very low overhead to provide true on-demand desktops or as VMware is tagging it, Just-In-Time desktops.

On-demand desktops with View Composer..... not happening

On-demand desktops with View Composer….. not happening

In my health care days the non-president desktops and shift change always resulted it some blunt force trauma around 7 am and 7 pm when staff would start their day. They only real way to counter balance the added load of login storms was to make sure the desktops were pre-built. This of course means you need so have some desktops sitting around doing nothing waiting for the these two time periods in the day, or use generic logins and then the user never disconnects which was another bag of problems.

Instant-clones ability to clone a live running VM by simply quiescing the VM is really amazing. Have you ever changed the name of the a desktop and then windows tells you to reboot? If your like me your try to do 5 or 6 other things before you have to reboot which usually ends up in a mess. Instant-clones uses a feature called clone prep to add the VM to AD and change it’s name, all while not having to reboot the VM. When you see a power on operation inside of vCenter it’s actually just quiescing the desktop so there is very low overhead.

The steps during Clone Prep. MS does not support Clone Prep but they didn't for View Composer so I don't see it being any different.

The steps during Clone Prep. MS does not support Clone Prep but they didn’t for View Composer so I don’t see it being any different.

When I went to test instant-clones I wanted to see if on-demand desktops was actually possible without destroying node densities. I had two test runs with Login VSI, 1 run with 400 knowledge users with all the desktops pre-deployed and 1 run with 400 knowledge users but I only started with 50 desktops. I had set the desktop pool to always have at least 30 free desktops until the pool got to 400 desktops.

Instant-clones delivers on-demand desktops with very low overhead.

Instant-clones delivers on-demand desktops with very low overhead.

The darker blue line represents the on-demand test and you can see that the impact over 400 hundred users is pretty small. This is pretty remarkable from a CPU and memory consumption on boot that is being almost eliminated.

It’s not all unicorns and rainbows however, instant clones does have some limitations in the first release:

No dedicated Desktop Pools
No RDS Desktop or Application Pools
Limited SVGA Support – Fixed max resolution & number of monitors
No 3D Rendering / GPU Support
No Sysprep support – Single SID across pool
No VVOL or VAAI NFS Hardware Clones support (Smaller desktops pools may take longer to provision)
No Powershell
No Multi-VLAN Support in a single Pool
No Reusable Computer Accounts
No Persistent Disks – Use Writable Volumes \ Flex App \ Unidesk \ RES …….

vMotion Is supported

Like anything use case will dictate when this gets used but its a powerful tool inside of Horizon. I plan to show some of the differences between View Composer and Instant Clones in my next posts. Also keep in mind that you still need high IO to service your desktops. Size for the peaks or face the wrath of your end users.