Skip to content

CombinedTempDiskAndCachedIOPS value for FX-series VMs mismatches the Azure documentation #28402

@mishafg

Description

@mishafg

Describe the bug

Fx-series VMs Azure CLI values mismatch the documentation. For example:

Standard_FX24mds in the documentation has "Max cached and temp storage throughput: 200000 IOPS.

However, in the Azure CLI the values are:
{
"name": "CombinedTempDiskAndCachedIOPS",
"value": "327000"
},

Related command

az vm list-skus --location eastus --size Standard_FX24mds --output json

Errors

Max cached and temp storage throughput documentation value is 200000, but the CombinedTempDiskAndCachedIOPS is 327000 from Azure CLI.

Issue script & Debug output

$ az vm list-skus --location eastus --size Standard_FX24mds --output json
[
{
"apiVersions": null,
"capabilities": [
{
"name": "MaxResourceVolumeMB",
"value": "1032192"
},
{
"name": "OSVhdSizeMB",
"value": "1047552"
},
{
"name": "vCPUs",
"value": "24"
},
{
"name": "MemoryPreservingMaintenanceSupported",
"value": "True"
},
{
"name": "HyperVGenerations",
"value": "V2"
},
{
"name": "MemoryGB",
"value": "504"
},
{
"name": "MaxDataDiskCount",
"value": "32"
},
{
"name": "CpuArchitectureType",
"value": "x64"
},
{
"name": "LowPriorityCapable",
"value": "True"
},
{
"name": "PremiumIO",
"value": "True"
},
{
"name": "VMDeploymentTypes",
"value": "IaaS"
},
{
"name": "vCPUsAvailable",
"value": "24"
},
{
"name": "ACUs",
"value": "310"
},
{
"name": "vCPUsPerCore",
"value": "2"
},
{
"name": "CombinedTempDiskAndCachedIOPS",
"value": "327000"
},
{
"name": "CombinedTempDiskAndCachedReadBytesPerSecond",
"value": "2057306112"
},
{
"name": "CombinedTempDiskAndCachedWriteBytesPerSecond",
"value": "2057306112"
},
{
"name": "CachedDiskBytes",
"value": "1159640000000"
},
{
"name": "UncachedDiskIOPS",
"value": "40000"
},
{
"name": "UncachedDiskBytesPerSecond",
"value": "629145600"
},
{
"name": "EphemeralOSDiskSupported",
"value": "True"
},
{
"name": "EncryptionAtHostSupported",
"value": "True"
},
{
"name": "CapacityReservationSupported",
"value": "True"
},
{
"name": "AcceleratedNetworkingEnabled",
"value": "True"
},
{
"name": "RdmaEnabled",
"value": "False"
},
{
"name": "MaxNetworkInterfaces",
"value": "4"
}
],
"capacity": null,
"costs": null,
"family": "standardFXMDVSFamily",
"kind": null,
"locationInfo": [
{
"location": "eastus",
"zoneDetails": [
{
"Name": [
"3"
],
"capabilities": [
{
"name": "UltraSSDAvailable",
"value": "True"
}
],
"name": null
}
],
"zones": [
"3"
]
}
],
"locations": [
"eastus"
],
"name": "Standard_FX24mds",
"resourceType": "virtualMachines",
"restrictions": [],
"size": "FX24mds",
"tier": "Standard"
}
]

Expected behavior

  {
    "name": "CombinedTempDiskAndCachedIOPS",
    "value": "200000"
  },

Environment Summary

$ az --version
azure-cli 2.57.0

core 2.57.0
telemetry 1.1.0

Extensions:
image-copy-extension 0.2.9

Dependencies:
msal 1.26.0
azure-mgmt-resource 23.1.0b2

Python location '/usr/local/Cellar/azure-cli/2.57.0/libexec/bin/python'
Extensions directory '~/.azure/cliextensions'

Python (Darwin) 3.11.7 (main, Dec 4 2023, 18:10:11) [Clang 15.0.0 (clang-1500.1.0.2.5)]

Legal docs and information: aka.ms/AzureCliLegal

Additional context

It looks like this is related to all the FX-series VMs, and not just Standard_FX24mds.

Metadata

Metadata

Labels

Auto-AssignAuto assign by botAzure CLI TeamThe command of the issue is owned by Azure CLI teamComputeaz vm/vmss/image/disk/snapshotcustomer-reportedIssues that are reported by GitHub users external to the Azure organization.potential-pruningquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions