Server Fault is a question and answer site for system and network administrators. It only takes a minute to sign up.
Sign up to join this community
Slightly related to a previous question about thick vs thin provisioning, why does eager zeroing the to-be-cloned VM take longer than lazy zeroing?
For example, in a recent test we ran, an eager-zeroed clone took ~85 minutes to complete, whereas changing to lazy zeroing made it complete in ~50 minutes.
How much overhead is incurred when eager zeroing vs lazy?
When would 'eager' be the right mode to use?
Eager Zeroing writes 0s to all empty blocks. This slightly increases performance later on when those blocks need to be written to for the first time.
Lazy Zeroing does nothing to the unallocated blocks. If you have an 80GB VMDK and only 10GB worth of data, only 10GB worth of blocks are used and the rest is left as-is until needed. If this example were eager zeroed, at the time of creation all 80GB would be written to, with zeroes filling the remaining 70GB.
If you're using thin provisioning at the storage level, you want to avoid eager zeros, as that will completely defeat the purpose of thin provisioning.
When would 'eager' be the right mode to use?
Eager is the right mode to use when you're not thin provisioning LUNs and you don't mind waiting a bit longer for the VMDK to be created.
Im rephrasing and reducing this to be a bit to be less confusing:
When would 'eager' be the right mode to use?
When you are Using Deduplication, Compression, or Thin Luns, on your SAN underlying the VMFS Store, instead of or in addition to, using Thin Provisioned VMs.
Usually you would only use this when reclaiming all of the free space in a vmfs volume by creating an extra Disk deployed this way.
Eager Zero is used for zeroing the space used by the VMDK on the VMFS store, and isn't really useful on a deployment of a new VM.
The classic example on why else you might use it was always pretty extreme/niche, and even more so today.
That is:
To pre-zero the sectors that will be written to by the VM, so that when the VM is running, it reduces VCPU load and disk write latency when writing 0s to the disk.
However this benefit is only while the VM writes to unused sections of disk, and so applications that were write-once read many would see the largest benefit.