SIOC Best Practice?

julez66 — Thu, 22 May 2014 17:22:26 GMT

So I've been reading the forums and various articles about SIOC, and it seems to be a mixed bag on when to use it, on what type of array to use it, etc.

So I was interested in what default suggestion is for Nimble Storage arrays when it comes to SIOC.

What kind of workloads? Enable it on all datastores? If you have mixed volumes of VMFS and Guest iSCSI connections on the same array?

Knowing that all spindles are being utilized I wasn't sure when this would be beneficial.

Re: SIOC Best Practice?

pdavies34 — Wed, 28 May 2014 14:36:28 GMT

Julez,

Taken from our VMWare BPG - avaialbe on InfoSight BPG page:

Storage IO Control (SIOC)

Storage IO Control (SIOC) enables QoS (Quality of Service) for shared storage access between virtual machines. It is purpose built to address the “noisy neighbor” problem that is common in shared services environments. One can define shares and IOPS limits on a per virtual machine VMDK level, to ensure critical virtual machines are treated as first class citizen.

Nimble Storage Consideration:

No additional configuration is needed on the Nimble array side to take advantage of this feature. Simply set higher share values and IOPS limits for mission critical virtual machines, and the I/O QoS enforcement would work accordingly.

So feel free to use it on a per VM basis if you feel it is required.

Phil

topic SIOC Best Practice? in Array Performance and Data Protection

SIOC Best Practice?

Re: SIOC Best Practice?