Skip to content

Commit 5448326

Browse files
Update common-questions-discovery-assessment.md
1 parent 35d0522 commit 5448326

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/migrate/common-questions-discovery-assessment.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -40,8 +40,8 @@ Yes, Azure Migrate needs vCenter Server to perform discovery in a VMware environ
4040
With as-on-premises sizing, Azure Migrate doesn't consider VM performance data for assessment. It assesses VM sizes based on the on-premises configuration. With performance-based sizing, sizing is based on utilization data.
4141

4242
- For example, if an on-premises VM has 4 cores and 8 GB of memory at 50% CPU utilization and 50% memory utilization, the following will occur:
43-
- As-on-premises sizing will recommend an Azure VM SKU that has four cores and 8 GB of memory.
44-
- Performance-based sizing will recommend a VM SKU that has two cores and 4 GB of memory, because the utilization percentage is considered.
43+
- As-on-premises sizing will recommend an Azure VM SKU that has 4 cores and 8 GB of memory.
44+
- Performance-based sizing will recommend a VM SKU that has 2 cores and 4 GB of memory, because the utilization percentage is considered.
4545

4646
- Similarly, disk sizing depends on two assessment properties: sizing criteria and storage type.
4747
- If the sizing criteria is performance-based and the storage type is automatic, Azure Migrate takes the IOPS and throughput values of the disk into account when it identifies the target disk type (standard or premium).

0 commit comments

Comments
 (0)