Feedback
Changelog

Have something to say?

Tell us how we could make the product more useful to you.

Default OS Disk Size (1023 GiB) in JSON exports does not reflect Azure reality

Hi Cloudprice Team, First off, thank you for the incredible resource. It’s a staple for SKU comparison. However, I’ve noticed an inconsistency regarding the OS Disk Size (GiB) field that is causing issues when using the site’s JSON data for automation or cost modeling. The Issue: On Cloudprice.net, the default OS Disk Size is listed as 1023 GiB for nearly all SKUs. In the actual Azure environment, there is no single "default" disk size; it is determined by the specific Image (Marketplace or Custom) being deployed—often 30 GiB for Windows or 128 GiB for certain Linux distros. Why this matters: When downloading the JSON file for VM SKUs, the osDiskSize (or equivalent field) defaults to 1023 GiB. This leads to: Inaccurate Costing: Users may accidentally calculate storage costs based on a 1 TB P30 disk rather than the standard 30–128 GiB disks. Integration Errors: Scripts relying on this JSON data for deployment templates may attempt to provision unnecessarily large (and expensive) disks. Suggested Improvement: Change the default display/export value from 1023 to "Varies by Image" or null. Alternatively, provide a note in the export documentation clarifying that 1023 GiB represents the maximum supported OS disk size for the SKU, rather than the default provisioned size. Has anyone else encountered this while parsing the SKU data, or is there a plan to align these values more closely with Azure's "Size-less" disk defaults? Best regards, Miguel

Miguel Abulencia About 1 month ago

Azure Res Disk Size (SCSI/NVMe)

Hi, I am a frequent user of the Azure VM Comparison page. Azure temporary disks are listed in Res Disk Size (GiB) without distinguishing between SCSI and NVMe, but it would be useful to provide a way to distinguish between SCSI and NVMe, since NVMe temporary disks require formatting with the script and are different in usability from SCSI disks. Please consider this.

Matsubara 9 months ago

Completed

Showing wrong pricing for GCP instances

For example: c4a-standard-1 in us-east4 shows at $120.38/mo (sustained discount) https://cloudprice.net/gcp/compute/instances/c4a-standard-1?paymentType=SustainedDiscounts100&timeoption=month GCP calculator shows the same instance at $33.58/mo https://cloud.google.com/products/calculator?hl=en&dl=CjhDaVEwTW1KbFptTmxaaTB3WVRSaUxUUXlaV0l0WWpJeU9TMHhaREF3WTJSbFkyRmlNRFVRQVE9PRAIGiREMTFEMDk3Ny0zRDVDLTRBMTgtQjRBMi0xNUM4NDZFODU0Qzg Am I missing anything ?

Yaron Dolev About 1 year ago

2

Completed

Show overall avearge on spot instance charts.

When plotting spot instance prices over time (e.g. for 1 year), it would be useful to display the overall average across the plotted period. A valuable use case for these charts is to ask “what is the average spot price for this give instance type and region over an entire year?”. While the data to compute this is available in its raw form, showing the result would save a lot of work.

Gil Tene About 1 year ago

2

Azure Performance Data Unreliable/Outdated

https://cloudprice.net/performance references this Azure documentation page as the source for performance data. However, Azure has stopped updating this page and the header on top as of today says it’s archived as of December 16, 2024. VM comparisons also reference this data, even showing for VMs that are not documented at all (like the Dadsv6 family, for example). Can these data be replaced by another source? If not, should it be removed until a new source is available?

ajruffinAMD About 1 year ago

2