- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Array Performance and Data Protection
- >
- SIOC Best Practice?
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-22-2014 10:22 AM
05-22-2014 10:22 AM
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.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2014 07:36 AM
05-28-2014 07:36 AM
SolutionJulez,
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