When you have provisioned All-SSD high performance storage, you can assign IOPS for virtual machines by using one of the following methods:

You can manually set an IOPS value when adding a VMDK to a virtual machine. See Modifying Virtual Machine Hard Disks for information.

When creating or editing an Organization VDC, you specify a default storage profile and IOPS value for VMDKs. (See Provision Storage for a Virtual Data Center.) When adding a VMDK to a virtual machine, you can select the “(Use VM default)” option so that the VMDK is assigned the default you configured for the Organization VDC.

Note

If you exceed the IOPS quota for the Organization VDC, you receive an error message.

You can configure a VMDK to use the amount of IOPS an application requires as it runs on the virtual machine. For example, a customer can purchase 6000 IOPS and choose not to distribute it to virtual machines. Instead, the customer can configure the VMDKs to utilize as much of the IOPS out of the 6000 IOPS quota that is available. To do this, when you create a VMDK, select an All-SSD high performance storage profile and set the IOPS value to zero (0). On the backend, the LUN is set so that it distributes the 6000 IOPS to the virtual data centers for that Organization and does not limit the IOPS assignment for the VMDKs that have a zero quota.

When choosing which method to assign IOPS to VMDKs, you set a majority of the VMDKs to 0 IOPS so that they utilize IOPS as needed. However, you manually assign VMDKs specific IOPS values when they run mission critical applications, such as payroll and month end processing, to ensure that these applications run with the amount of IOPS they require.

VM1

Disk C: SSD-Accelerated 50GB system disk

Some files need very low latency while other files are rarely used; however, because the files are commingled on the same disk, placing them on the SSD-Accelerated tier (which handles both needs) is preferable.

 

Disk D: Basic 1TB for archiving logs and reports

 

Disk E: All-SSD – Premium 200GB for the database

This disk has the IOPS quota set to 0 so that the application utilizes as much of the IOPS out of the quota that is available.

VM2

Disk C: All-SSD – Standard 500GB with 1750 IOPS

This disk is assured a minimum level of IOPS to support the caching and updating for this application; the system disk also buffers for the cache on this application.

 

Disk D: SSD-Accelerated 2TB

This disk is a second tier of file storage. It is fast to get into the cache and supports fast writes to purge the cache.

 

Disk E: Basic 8TB archived versions of the files updated by the application

VM3

Disk C: SSD-Accelerated 50GB system disk

 

Disk D: All SSD Premium – 800GB with 4000 IOPS to ensure the custom application on this virtual machine gets the I/O that it needs

 

Disk E: All SSD Premium – 100GB with 500 IOPS for the small database with financial data

 

Disk F: Basic – 2TB log files from the application; keep for 24 hours and then delete