Which vMotion configuration minimizes VM stun duration for latency-sensitive apps?

When migrating a powered-on virtual machine between ESXi hosts in a vSphere environment, the final memory synchronization phase involves a brief period where the VM is paused, known as the stun period. For small applications with strict latency requirements, this pause can potentially trigger application-level timeouts or disconnects.

The duration of this stun is influenced by the rate of memory page changes and the available bandwidth on the vMotion VMkernel network. While shared storage simplifies the process, the transition of the device state remains a critical point of uncertainty regarding perceived downtime.

• What specific vMotion network throughput thresholds are required to ensure the stun period remains below a millisecond threshold?
• Does the use of Enhanced vMotion Compatibility (EVC) introduce any measurable overhead to the final synchronization phase?