There are two things that should be changed then: For example as mentioned in VMware KB here, large-scale workloads with intensive I/O patterns might require queue depths significantly greater than Paravirtual SCSI default values. Sometimes it may be necessary to adjust ESXi/ESX hosts maximum queue depth values. For example, the HP Smart Array P420 Queue Depth can be 1011 or 1020: Queue Depth tuning on vSphere You should use IO Controller being on the VMware HCL. Of course, Queue Depth is crucial when you implement VSAN. L = Number of LUNs presented to the host via the array target portĪs shown above, it is recommended that the total aggregate of the maximum number of outstanding SCSI commands from all ESXi hosts connected to a port of an array should be less than the maximum queue depth of the port. P = Number of host paths connected to the array target port Port-QD => ESXi Host 1 (P * QD * L) + ESXi Host 2 (P * QD * L). What's about VMware infrastructure and multiple ESXi hosts communicating with the storage ports? The Queue Depth should be calculated by the following formula: The fan-out ratio is 16:1 meaning 16 initiators per storage port. ( 8 x 1024) / 64 = 128 single connected servers or 64 (2 x HBA) or 32 (4 x HBA) So for example, we have an 8 port array (4 ports per controller) with 1024 queues per storage port and a host (LUN) queue depth setting of 64 will be able to connect up to: (Queues Depth per Physical Storage Port x Storage Ports) / Host Queue Depth = Number of servers
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |