Skip to content

Commit 9da2592

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

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
@@ -449,7 +449,7 @@ Hyperconvergence can improve performance by co-locating workloads with their sto
449449

450450
* **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.
451451

452-
### Enable Hyperconvergence in Azure Container Storage
452+
### Enable hyperconvergence in Azure Container Storage
453453

454454
Hyperconvergence is enabled by default for NVMe and temporary disk storage pools with only one replica. This ensures optimized data locality and improved performance for single-replica configurations. For multi-replica setups, hyperconvergence isn't enabled by default but can be configured using the `hyperconverged` parameter in the StoragePool specification.
455455

0 commit comments

Comments
 (0)