Hi Friend,
DPM puts standby host to ACPI S5 state which is just above the mechanical power off, it is mean that DPM tries to save as max power as possible.
"The reason VMware DPM evacuates hosts and powers them down to the ACPI S5 state is that hosts typically
use 60 percent or more of their peak power when totally idle, so the power savings possible with this approach
are substantial. Vacating a host and placing it in a lighter sleep state than S5, such as the ACPI S3
“suspend-to-RAM” state, can consume an order of magnitude more power than ACPI S5 because of the need to
keep the host’s RAM powered on.
Plz refer attached image for more details.
If DPM puts host to ACPI S3 level, then host would take less time to get powered ON. But in the current design its not available to set DPM to ACPI S3 level.
One more reason DPM takes more time to power on the host, If host has too many data stores attached to it. It does take more time to get powered ON.
Also DPM uses 3 protocols :
VMware DPM can use one of three power management protocols to bring a host out of standby mode: Intelligent Platform Management Interface (IPMI), Hewlett-Packard Integrated Lights-Out (iLO), or Wake-On-LAN (WOL). Each protocol requires its own hardware support and configuration. If a host does not support any of these protocols it cannot be put into standby mode by VMware DPM. If a host supports multiple protocols, they are used in the following order: IPMI, iLO, WOL.
I suggest you to try enabling each one and compare, we may get some improvement over other.
Please refer below KB: VMware KB: Configuring vSphere Distributed Power Management advanced settings to customize host power-on and power-o…
This KB can satisfy your requirement by some other way for sure. Just play with all advanced options available@KB
If this info is useful, please award points as appropriate.
Message was edited by: Vikas