Merge pull request #280977 from seligj95/vcores

Vcores

Author: prmerger-automator[bot]

articles/app-service/environment/upgrade-to-asev3.md

@@ -55,6 +55,18 @@ There are two automated migration features available to help you upgrade to App
 - **Side-by-side migration feature** creates a new App Service Environment v3 in a different subnet that you choose and recreates all of your App Service plans and apps in that new environment. Your existing environment is up and running during the entire migration. Once the new App Service Environment v3 is ready, you can redirect traffic to the new environment and complete the migration. There's no application downtime during the migration. For more information about this feature, see [Automated upgrade using the side-by-side migration feature](side-by-side-migrate.md).
 - **Manual migration options** are available if you can't use the automated migration features. For more information about these options, see [Migration alternatives](migration-alternatives.md).
 
+### Why do some customers see performance differences after migrating?
+
+App Service Environment v3 uses newer virtual machines that are based on virtual CPUs (vCPU), not physical cores. One vCPU typically doesn't equate to one physical core in terms of raw CPU performance. As a result, CPU-bound workloads might see a performance difference if attempting to match old-school physical core counts to current vCPU counts.
+
+When migrating to App Service Environment v3, we map App Service plan tiers as follows: 
+
+|App Service Environment v2 SKU|App Service Environment v3 SKU|
+|------------------------------|------------------------------|
+|I1                            |I1v2                          |
+|I2                            |I2v2                          |
+|I3                            |I3v2                          |
+
 ### Migration path decision tree
 
 Use the following decision tree to determine which migration path is right for you.

articles/app-service/environment/version-comparison.md

@@ -2,7 +2,7 @@
 title: 'App Service Environment version comparison'
 description: This article provides an overview of the App Service Environment versions and feature differences between them.
 author: seligj95
-ms.date: 4/22/2024
+ms.date: 7/16/2024
 ms.author: jordanselig
 ms.topic: article
 ---
@@ -29,6 +29,7 @@ There's a new version of App Service Environment that is easier to use and runs
 |---------|---------|---------|---------|
 |Hardware     |[Cloud Services (classic)](../../cloud-services/cloud-services-choose-me.md)  |[Cloud Services (classic)](../../cloud-services/cloud-services-choose-me.md)  |[Virtual Machine Scale Sets](../../virtual-machine-scale-sets/overview.md)  |
 |[Available SKUs](https://azure.microsoft.com/pricing/details/app-service/windows/)  |P1, P2, P3, P4         |I1, I2, I3         |I1v2, I2v2, I3v2, I4v2, I5v2, I6v2        |
+|CPU|Physical cores|Physical cores|Virtual CPu (vCPU)|
 |Maximum instance count     |55 hosts (default front-ends + workers)         |100 instances per App Service plan. Maximum of 200 instances across all plans.         |100 instances per App Service plan. Maximum of 200 instances across all plans.         |
 |Zone redundancy     |No         |No - [zone pinning](zone-redundancy.md) to one zone is available         |[Yes](../../reliability/migrate-app-service-environment.md)         |
 |Dedicated host group     |No         |No         |[Yes](creation.md#deployment-considerations) (not compatible with zone redundancy)         |