Azure VM High Disk Throughput, Upgrade Disk Tier
The disk is at its throughput cap, so I/O is throttled and the application spends its time waiting on storage rather than doing work.
Free to start. No card. The playground just needs your work email.
Azure
Found, explained, handed over.
What we would change and why, with no savings claim and no policy behind it.
Detect
ZopNight checks this automatically across Azure, with read-only access to the account.
Explain
Every finding says exactly what to change: Upgrade the VM's disk tier.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Virtual Machines on Azure
- The fix, by hand
- Open VM → Disks; cross-reference each disk SKU with its IOPS + throughput metrics in Monitor (namespace = Disks).
- Identify disks on Standard HDD / Standard SSD that show sustained queue depth or throttle events.
- For data disks, you can change SKU online from Standard → Premium SSD or Premium SSD v2 via Disk → Size + performance.
- For the OS disk, stop the VM, change the SKU, then start.
- Validate I/O latency drops in Monitor → Metrics after the change.
- Premium SSD v2 is usually the better target than Premium SSD for new workloads: independent IOPS / throughput dials, no SKU jumps.
These are the steps the finding carries in the product.
- Category
- Performance. A measured bottleneck worth clearing: throttled operations, undersized tiers, a workload near its limit.
- Where it appears
- The Advisory tab of Recommendations, with every affected resource listed.
- Rule ID
RC-264- Full reference
Related checks
See the performance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.