text: **3.12.1 Queue depth**
  
  Typically, hosts issue subsequent I/O requests to storage systems without waiting for 
  completion of previous ones. The number of outstanding requests is called*queue depth*. 
  Sending multiple I/O requests in parallel (asynchronous I/O) provides significant performance 
  benefits compared to sending them one-by-one (synchronous I/O). However, if the number of 
  queued requests exceeds the maximum that is supported by the storage controller, you 
  experience performance degradation. 
  
  Therefore, for large storage networks, plan for setting correct SCSI commands queue depth 
  on your hosts. For this purpose, a large storage network is defined as one that contains at 
  least 1000 volume mappings. For example, a deployment with 50 hosts with 20 volumes 
  mapped to each of them is considered a large storage network. For more information about 
  the queue depth calculations, search for “Queue depth in large SANs” at this IBM Knowledge 
  Center web page. 
  
  **3.12.2 Offloaded data transfer**
  
  If your Windows hosts are configured to use Microsoft Offloaded Data Transfer (ODX) to 
  offload the copy workload to the storage controller, consider the benefits of this technology 
  against extra load on storage controllers. The benefits and effects of enabling ODX are 
  especially prominent in Microsoft Hyper-V environments with ODX enabled. 