[CLOUDSTACK-9428] Fix for CLOUDSTACK-9211 - Improve performance

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Component/s: VMware
• Security Level: Public (Anyone can view this level - this is the default.)
• Flags: Patch
• Assignee: Nicolas Vazquez
• Reporter: Nicolas Vazquez
• Created: 05/Jul/16 22:20
• Updated: 02/Mar/17 20:17
• Resolved: 02/Mar/17 20:17

Description

Introduction

On CLOUDSTACK-9211 passing vRAM size to support 3D GPU problem was addressed on VMware. It was found out that it could be improved to increase performance by reducing extra API calls, as we'll describe later

Improvement

On WMware, VmwareResource manages execution of StartCommand. Before sending power on command to ESXi hypervisor, vm is configured by calling reconfigVMTask web method on vSphere's client VimPortType web service.
It was found out that we were using this method 2 times when passing vRAM size, as it implied creating a new vm config spec only editing video card specs and making an extra call to reconfigVMTask.

We propose reducing the extra web service call by adjusting vm's config spec. This way video card gets properly configured (when passing vRAM size) in the same configure call, increasing performance.

Use case (passing vRAM size)

1. Deploy a new VM, let its id be X
2. Stop VM
3. Execute SQL, where X is vm's id and Z is vRAM size (in kB):

   INSERT INTO cloud.user_vm_details (vm_id, name, value) VALUES (X, 'mks.enable3d', 'true');
   INSERT INTO cloud.user_vm_details (vm_id, name, value) VALUES (X, 'mks.use3dRenderer', 'automatic');
   INSERT INTO cloud.user_vm_details (vm_id, name, value) VALUES (X, 'svga.autodetect', 'false');
   INSERT INTO cloud.user_vm_details (vm_id, name, value) VALUES (X, 'svga.vramSize', Z);
   

4. Start VM

Issue Links

• links to: GitHub Pull Request #1605