#VCP #Storage #Concept Similar like [[vSphere - Network IO Control (NIOC|vSphere - Network IO Control (NIOC|[NIOC)]]]].md) . Can be enabled on datastores or datastore clusters. SIOC is based mostly on latency and throttles VMs based on the consumption of IOPS. It prioritizes IO to allow for workload consolidation. Like with [[vSphere - Network IO Control (NIOC|vSphere - Network IO Control (NIOC|[NIOC)]]]].md) SIOC will only go into effect once there is congestion. Congestion is determined with latency measured on each datastore. You can configure a threshold of latency, once the latency in ms is higher than the threshold SIOC will go into action. General guidance says that anything above 50ms latency on a disk is probably prolematic. ## Shares Can be configured on each VM on a Datastore. Is only acted upon once the threshold of our SIOC is exceeded. VM storage policies are assigning limits for each VM. ## Storage Policy Based Management(SPBM) Allows for assigning policies for VMs which is enforced by Storage DRS. ## 🔗Resources