# Data Object - LatencySensitivity(vim.LatencySensitivity)

Property of
  VirtualMachineConfigInfo, VirtualMachineConfigSpec
Extends
  DynamicData
See also
  LatencySensitivitySensitivityLevel
Since
  vSphere API 5.1

## Data Object Description

Specification of the latency-sensitivity information.

The latency-sensitivity is used to request from the kernel a constraint on the scheduling delay of the virtual CPUs or other resources. This allows latency-sensitive applications(e.g. VOIP, audio/video streaming, etc.) to run in a virtual machine which is configured to use specific scheduling latencies and to be scheduled with low latency.

The kernel does not provide any guarantee that it will meet the latency-sensitivity requirement of a virtual machine CPU or other resources but it will always accept the latency-sensitivity value provided.

Properties

Name | Type | Description
--- | --- | ---
level | LatencySensitivitySensitivityLevel | The nominal latency-sensitive level of the application.
sensitivity* | xsd:int | Deprecated. As of vSphere version 5.5, this field is deprecated. The custom absolute latency-sensitivity value of the application. This value will be used only when the latency-sensitivity level property is is set to `custom`. It is ignored in all other cases. The unit of this value is micro-seconds and the application is more latency sensitive when this value is smaller. For example, if the absolute latency-sensitivity is 2000us, the kernel will try to schedule the virtual machine in a way so that its scheduling latency is not more than 2ms.
Properties inherited from DynamicData
None

*Need not be set
Show WSDL type definition
<complexType xmlns="http://www.w3.org/2001/XMLSchema" xmlns:vsan="urn:vsan" name="LatencySensitivity"> <complexContent> <extension base="vsan:DynamicData"> <sequence> <element name="level" type="vsan:LatencySensitivitySensitivityLevel"/> <element name="sensitivity" type="xsd:int" minOccurs="0"/> </sequence> </extension> </complexContent> </complexType>