Skip to content

Commit 140cf4e

Browse files
authored
Update use-container-storage-with-local-disk.md
Remove performance numbers from the perf optimization table. Correct numbers will be updated later
1 parent d9dfa75 commit 140cf4e

File tree

1 file changed

+17
-1
lines changed

1 file changed

+17
-1
lines changed

articles/storage/container-storage/use-container-storage-with-local-disk.md

Lines changed: 17 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -400,7 +400,23 @@ kubectl delete sp -n acstor <storage-pool-name>
400400

401401
### Optimize performance when using local NVMe
402402

403-
[!INCLUDE [container-storage-nvme-performance](../../../includes/container-storage-nvme-performance.md)]
403+
Depending on your workload’s performance requirements, you can choose from three different performance tiers: **Basic**, **Standard**, and **Advanced**. These tiers offer a different range of IOPS, and your selection will impact the number of vCPUs that Azure Container Storage components consume in the nodes where it's installed. Standard is the default configuration if you don't update the performance tier.
404+
405+
| **Tier** | **Number of vCPUs** |
406+
|---------------|--------------------------|
407+
| `Basic` | 12.5% of total VM cores |
408+
| `Standard` (default) | 25% of total VM cores |
409+
| `Advanced` | 50% of total VM cores |
410+
411+
> [!NOTE]
412+
> RAM and hugepages consumption will stay consistent across all tiers: 1 GiB of RAM and 2 GiB of hugepages.
413+
414+
Once you've identified the performance tier that aligns best to your needs, you can run the following command to update the performance tier of your Azure Container Storage installation. Replace `<performance tier>` with basic, standard, or advanced.
415+
416+
```azurecli-interactive
417+
az aks update -n <cluster-name> -g <resource-group> --enable-azure-container-storage <storage-pool-type> --ephemeral-disk-nvme-perf-tier <performance-tier>
418+
```
419+
404420

405421
## See also
406422

0 commit comments

Comments
 (0)