Queue depth calculation for target and initiators.
What is Queue depth? It is the number of I/O operations that can run in parallel on a LUN/blocks. Generally, it specifies the number of outstanding requests per LUN. It is the number of I/O requests that the initiator can send and receive per LUN. Each I/O request from the host’s initiator HBA to the storage target adapter ingests a queue entry. Typically, a higher queue depth equates to improved performance. However, if the storage controller’s maximum queue depth is reached, that storage controller discards incoming I/O request by returning queue full response to the initiator, causing bottlenecks and latency issues. The following general recommendations can be made about "tuning" queue depths. For small to mid-size systems, use a HBA queue depth of 32. For large systems, use a HBA queue depth of 128. For exception cases or performance testing, use a queue depth of 256 to avoid possible queuing problems. All hosts should have the queue d...
Comments
Post a Comment