As a best practice, use the default virtual disk format of thick provision lazy zeroed unless there are specific needs to pre-allocate virtual disk storage such as Microsoft clustering, VMware Fault Tolerance (FT), or for virtual machines that may be impacted by the thin or zeroedthick on-first-write penalties. If the application is sensitive to VMFS write penalties, it is recommended to test eagerzeroedthick virtual disks to determine the actual performance impact.
And you should consider this from a SC point of view->
SC Series thin write functionality:
Most versions of SCOS have the ability to detect incoming sequential zeroes while being written and track them, but not actually write the zeroed page to the physical disks. When creating virtual disks on these versions of firmware, all virtual disk formats will be thin provisioned at the array level, including thick provision eager zeroed.
littlesteve
4 Posts
0
August 29th, 2017 12:00
This is the best practice ->
As a best practice, use the default virtual disk format of thick provision lazy zeroed unless there are specific needs to pre-allocate virtual disk storage such as Microsoft clustering, VMware Fault Tolerance (FT), or for virtual machines that may be impacted by the thin or zeroedthick on-first-write penalties. If the application is sensitive to VMFS write penalties, it is recommended to test eagerzeroedthick virtual disks to determine the actual performance impact.
And you should consider this from a SC point of view->
SC Series thin write functionality:
Most versions of SCOS have the ability to detect incoming sequential zeroes while being written and track them, but not actually write the zeroed page to the physical disks. When creating virtual disks on these versions of firmware, all virtual disk formats will be thin provisioned at the array level, including thick provision eager zeroed.
Look at this doc also -> Understanding RAID with Dell SC Series Storage - White Papers ...