Skip to content

Commit 08d293b

Browse files
Update articles/storage/container-storage/use-container-storage-with-local-nvme-replication.md
Co-authored-by: Ken Downie <[email protected]>
1 parent 9da2592 commit 08d293b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/storage/container-storage/use-container-storage-with-local-nvme-replication.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -447,7 +447,7 @@ Consider enabling hyperconvergence for replicated volumes when:
447447

448448
Hyperconvergence can improve performance by co-locating workloads with their storage, but there are scenarios where it might not be ideal:
449449

450-
* **Potential Resource Imbalance**: While hyperconvergence itself does not limit the number of applications on a node, if multiple workloads create replicas on the same node and that node runs out of resources (CPU, memory, or storage bandwidth), some workloads may not be able to schedule there. As a result, they may end up running **without hyperconvergence**, despite it being enabled.
450+
* **Potential resource imbalance**: While hyperconvergence itself doesn't limit the number of applications on a node, if multiple workloads create replicas on the same node and that node runs out of resources (CPU, memory, or storage bandwidth), some workloads might not be able to schedule there. As a result, they might end up running **without hyperconvergence**, despite it being enabled.
451451

452452
### Enable hyperconvergence in Azure Container Storage
453453

0 commit comments

Comments
 (0)