Skip to content

Commit 1b1262a

Browse files
authored
Update acu.md
1 parent 1018b0c commit 1b1262a

File tree

1 file changed

+4
-7
lines changed
  • articles/virtual-machines

1 file changed

+4
-7
lines changed

articles/virtual-machines/acu.md

Lines changed: 4 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ ms.reviewer: davberg
1919
>
2020
> Azure is no longer publishing ACUs since the metric has limited ability to inform users of the expected performance of a virtual machine across various attributes. For the most accurate results on a specific virtual machine, Azure recommends users run their workload(s) on that virtual machine to verify performance.
2121
22-
The concept of the Azure Compute Unit (ACU) provides a way of comparing compute (CPU) performance across Azure SKUs. This helps you easily identify which SKU is most likely to satisfy your performance needs. ACU is currently standardized on a Small (Standard_A1) virtual machine being 100 and all other SKUs then represent approximately how much faster that SKU can run a standard benchmark.
22+
The concept of the Azure Compute Unit (ACU) provides a way of comparing compute (CPU) performance across Azure SKUs. The Azure Compute Unit enables you to easily identify which SKU is most likely to satisfy your performance needs. ACU is currently standardized on a Small (Standard_A1) virtual machine being 100 and all other SKUs then represent approximately how much faster that SKU can run a standard benchmark.
2323

2424
*ACUs use Intel® Turbo technology to increase CPU frequency and provide a performance increase. The amount of the performance increase can vary based on the virtual machine size, workload, and other workloads running on the same host.<br>
2525
**ACUs use AMD® Boost technology to increase CPU frequency and provide a performance increase. The amount of the performance increase can vary based on the virtual machine size, workload, and other workloads running on the same host.<br>
@@ -70,7 +70,7 @@ The concept of the Azure Compute Unit (ACU) provides a way of comparing compute
7070
| [Mv2](msv2-mdsv2-series.md) | 240 - 280 | 2:1\*\*\* |
7171
| [NVv4](nvv4-series.md) |230 - 260** | 2:1\*\*\*\* |
7272

73-
Processor model information for each SKU is available in the SKU documentation (see links above). Optimal performance may require the latest virtual machine images (OS and [virtual machine generation](generation-2.md)) to ensure the latest updates and fastest drivers.
73+
Processor model information for each SKU is available in the SKU documentation. Optimal performance may require the latest virtual machine images (OS and [virtual machine generation](generation-2.md)) to ensure the latest updates and fastest drivers.
7474

7575
### Virtual machine series retiring
7676

@@ -95,20 +95,17 @@ The following GPU series are also retiring.
9595
| NV | [August 31, 2023](nv-series-retirement.md) |
9696

9797
## Performance consistency
98+
Azure virtual machine sizes typically run with maximum performance on the hardware platform they're first released on. Azure may place controls on older Azure virtual machines when run on newer hardware to help maintain consistent performance for our customers even when the virtual machines run on different hardware. For example:
9899

99-
We understand that Azure customers want the best possible consistent performance and want to be able to count on getting the same performance from the same type of virtual machine every time.
100-
101-
Azure virtual machine sizes typically run with maximum performance on the hardware platform they're first released on. Azure may place controls on older Azure virtual machines when run on newer hardware to help maintain consistent performance for our customers even when the virtual machines run on different hardware. For example:
102100
1) **D**, **E**, and **F** series virtual machines may have the processor frequency set to a lower level when running on newer hardware to help achieve better performance consistency across hardware updates. (The specific frequency setting varies based on the processor the virtual machine series was first released on and the comparable performance of the current hardware).
103101
2) **A** series virtual machines use an older model based on time slicing newer hardware to deliver performance consistency across hardware versions.
104102
3) **B** series virtual machines are burstable and use a credit system (described in their [documentation](sizes-b-series-burstable.md) to achieve expected performance.
105103

106104
These different processor settings for virtual machines are a key part of Azure's effort to provide consistent performance and minimize the impact of changes in underlying hardware platform outside of our customer’s control.
107105

108-
109106
## More information
110107

111-
For more information about the different sizes see:
108+
For more information about the different sizes, see:
112109

113110
- [General-purpose](sizes-general.md)
114111
- [Memory optimized](sizes-memory.md)

0 commit comments

Comments
 (0)