Hitachi Dynamic Link Manager is being used with a Hitachi Unified Storage system in a multi-path environment with intense sequential I/Os. What are two recommended load-balancing algorithms? (Choose…

Question

Options

• Aleast I/Os
• Bleast blocks
• Cextended least I/Os
• Dextended round-robin

Explanation

For Hitachi Dynamic Link Manager (HDLM) with intense sequential I/Os, the two recommended algorithms are C (Extended Least I/Os) and D (Extended Round-Robin), because HDLM's "extended" variants are specifically optimized for sequential workloads - they factor in path weighting and pending queue depth to distribute large, ordered I/O streams more efficiently across available paths. Standard Least I/Os (A) is designed for random I/O environments where queue depth per path is the primary concern, making it suboptimal when I/Os are large and sequential. Least Blocks (B) measures pending byte volume rather than I/O count, which is similarly better suited to mixed or random workloads, not sustained sequential streams. The key insight is that the "extended" prefix in HDLM signals an algorithm tuned for sequential access patterns, while the non-extended versions target random I/O scenarios.

Memory tip: Think "Extended = Sequential" - whenever you see a sequential I/O workload question in HDLM, the answer will always be the two extended algorithms (Extended Least I/Os and Extended Round-Robin).

No community discussion yet for this question.