1 Copper

Unity best practises for LUN I/O for VMWARE

Unity 600 F I/O Control.

If anyone has any best practices  to share for storage I/O Control for VMWARE please let me know.

Below is what I found for I/O control as per below document .

  Host I/O limits Dell EMC recommends setting Host I/O limits on workloads that might monopolize pool resources and starve other applications of their required performance. Example: Limit the bandwidth available to large-block applications that may be increasing the latency on other small-block workloads. 

This other doc just talks about how to configure I/O Control.

Below blog it is mentioned if  we  create different pools for different environments. This way the workloads would be entirely separate and should not impact each other.

Tags (1)
0 Kudos
1 Reply
8 Krypton

Re: Unity best practises for LUN I/O for VMWARE

It would be helpful if you explained what you're try to accomplish. What do you mean by "Host IO Control" ? In ESX there is a setting called "IOPS Limit" - we recommend that you change that from the default of 1000 to 1. On the array you can set a "Host IO Limit". You can create separate Pools for different types of workload, you can configure the front-end ports to use certain ports for certain types of workload (segregate the large Read IO from the random Write IO).

There are a number of White Papers for Unity - you've listed a couple. There is a Best Practice Guide, there are Host Connectivity Guides for the different operating systems, there is On-Line Help for explaining how to setup things on the array. There are a number of White Papers available for specific applications such as Oracle, SQL, Exchange, for example. Just do a search for "Best Practices Unity" and you should see a number of articles.