Skip to content

Commit 7e70c06

Browse files
Merge pull request #285832 from kikucher/kikucher-patch-1
Updated performance tier in local NVMe documentation
2 parents 87efedf + 22fea8b commit 7e70c06

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

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

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

401401
### Optimize performance when using local NVMe
402402

403-
Depending on your workload’s performance requirements, you can choose from three different performance tiers: **Basic**, **Standard**, and **Advanced**. 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.
403+
Depending on your workload’s performance requirements, you can choose from three different performance tiers: **Basic**, **Standard**, and **Premium**. 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.
404404

405405
These three tiers offer a different range of IOPS. The following table contains guidance on what you could expect with each of these tiers. We used [FIO](https://github.com/axboe/fio), a popular benchmarking tool, to achieve these numbers with the following configuration:
406406
- AKS: Node SKU - Standard_L16s_v3;
@@ -410,12 +410,12 @@ These three tiers offer a different range of IOPS. The following table contains
410410
| --- | --- | --- | --- |
411411
| `Basic` | 12.5% of total VM cores | Up to 100,000 | Up to 90,000 |
412412
| `Standard` (default)| 25% of total VM cores | Up to 200,000 | Up to 180,000 |
413-
| `Advanced` | 50% of total VM cores | Up to 400,000 | Up to 360,000 |
413+
| `Premium` | 50% of total VM cores | Up to 400,000 | Up to 360,000 |
414414

415415
> [!NOTE]
416416
> RAM and hugepages consumption will stay consistent across all tiers: 1 GiB of RAM and 2 GiB of hugepages.
417417
418-
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.
418+
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 premium.
419419

420420
```azurecli-interactive
421421
az aks update -n <cluster-name> -g <resource-group> --enable-azure-container-storage <storage-pool-type> --ephemeral-disk-nvme-perf-tier <performance-tier>

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -420,18 +420,18 @@ kubectl delete sp -n acstor <storage-pool-name>
420420

421421
### Optimize performance when using local NVMe
422422

423-
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.
423+
Depending on your workload’s performance requirements, you can choose from three different performance tiers: **Basic**, **Standard**, and **Premium**. 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.
424424

425425
| **Tier** | **Number of vCPUs** |
426426
|---------------|--------------------------|
427427
| `Basic` | 12.5% of total VM cores |
428428
| `Standard` (default) | 25% of total
429-
| `Advanced` | 50% of total VM cores |
429+
| `Premium` | 50% of total VM cores |
430430

431431
> [!NOTE]
432432
> RAM and hugepages consumption will stay consistent across all tiers: 1 GiB of RAM and 2 GiB of hugepages.
433433
434-
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.
434+
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 premium.
435435

436436
```azurecli-interactive
437437
az aks update -n <cluster-name> -g <resource-group> --enable-azure-container-storage <storage-pool-type> --ephemeral-disk-nvme-perf-tier <performance-tier>

0 commit comments

Comments
 (0)