Goal

Customers need an easy way to define VM(s) with best practice tuning for I/O workloads – which includes net & blk multiqueue, multi IOthreads(4.19+), and appropriate cpu requests – without any requirements to change the host configuration.

User Stories

• As a Database Admin, I want to be able to define a VM (size of my choosing) that is appropriately tuned to perform well with heavy DB I/O load.
• As a customer evaluating a PoC, I want to easily define a VM that can perform competitively for low level I/O workloads such as fio.

Non-Requirements

• This VM definition should not require pinning (i.e. dedicatedCPUs) or explicit hugepage backing since these require host-level config changes, the goal of this definition is to make the VM bootable by default given a boot source is provided.

Notes

• Note, the multi IOthread (supplementalPool) feature is only available on 4.19+ (fyi, feature intro blog)

  ioThreadsPolicy: supplementalPool  
  ioThreads:
    supplementalPoolThreadCount: X