Dell PowerVault MD3200 Deployment Guide - Page 35

Appendix-Load Balancing, Windows Load Balance Policy, Round Robin With Subset, Least Queue Depth

Page 35 highlights

A Appendix-Load Balancing Windows Load Balance Policy Multi-path drivers select the I/O path to a virtual disk through a specific RAID controller module. When the multi-path driver receives a new I/O, the driver tries to find a path to the current RAID controller module that owns the virtual disk. If that path cannot be found, the multi-path driver migrates the virtual disk ownership to the secondary RAID controller module. When multiple paths to the RAID controller module that owns the virtual disk exist, you can choose a load balance policy to determine which path is used to process I/O. Multiple options for setting the load balance policies let you optimize I/O performance when mixed host interfaces are configured. You can choose one of the following load balance policies to optimize I/O performance: • Round robin with subset • Least queue depth with subset Round Robin With Subset The round-robin with subset I/O load balance policy routes I/O requests, in rotation, to each available data path to the RAID controller module that owns the virtual disks. This policy treats all paths to the RAID controller module that owns the virtual disk equally for I/O activity. Paths to the secondary RAID controller module are ignored until ownership changes. The basic assumption for the round-robin policy is that the data paths are equal. With mixed host support, the data paths might have different bandwidths or different data transfer speeds. Least Queue Depth With Subset The least queue depth with subset policy is also known as the least I/Os, or least requests, policy. This policy routes the next I/O request to a data path that has the least outstanding I/O requests queued. For this policy, an I/O request is simply a command in the queue. The type of command or the number of blocks that are associated with the command are not considered. Appendix-Load Balancing 35

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38

Appendix—Load Balancing
35
A
Appendix—Load Balancing
Windows Load Balance Policy
Multi-path drivers select the I/O path to a virtual disk through a specific
RAID controller module. When the multi-path driver receives a new I/O, the
driver tries to find a path to the current RAID controller module that owns
the virtual disk. If that path cannot be found, the multi-path driver migrates
the virtual disk ownership to the secondary RAID controller module. When
multiple paths to the RAID controller module that owns the virtual disk exist,
you can choose a load balance policy to determine which path is used to
process I/O. Multiple options for setting the load balance policies let you
optimize I/O performance when mixed host interfaces are configured.
You can choose one of the following load balance policies to optimize
I/O performance:
Round robin with subset
Least queue depth with subset
Round Robin With Subset
The round-robin with subset I/O load balance policy routes I/O requests, in
rotation, to each available data path to the RAID controller module that
owns the virtual disks. This policy treats all paths to the RAID controller
module that owns the virtual disk equally for I/O activity. Paths to the
secondary RAID controller module are ignored until ownership changes. The
basic assumption for the round-robin policy is that the data paths are equal.
With mixed host support, the data paths might have different bandwidths
or different data transfer speeds.
Least Queue Depth With Subset
The least queue depth with subset policy is also known as the least I/Os, or
least requests, policy. This policy routes the next I/O request to a data path
that has the least outstanding I/O requests queued. For this policy, an I/O
request is simply a command in the queue. The type of command or the
number of blocks that are associated with the command are not considered.