ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal To determine whether enabling Fully Automated DRS increases latency for concurrent vMotion requests compared to Partial Automation, and to identify the contributing factors. Constraints & Uncertainty Latency is only measurable under high concurrent migration loads. Network bandwidth and host CPU contention may vary across clusters. DRS imbalance thr
vSphere Distributed Power Management (DPM) can power down idle ESXi hosts in a DRS-enabled cluster, which may reduce power and footprint for low-traffic workloads. The unresolved decision is whether to run DPM in fully automated mode or manual recommendation mode when workload variability and SLA sensitivity are both present. DPM depends on cluster-level DRS
The goal is to identify the exact host memory utilization level at which vSphere DRS treats memory pressure as high enough to trigger automatic reclamation mechanisms such as ballooning, swapping, or VMotion-based load balancing. Currently, this threshold is not visible in the vSphere Client and is derived internally from a combination of active memory, swap
vsphere