GCP Disk SSD with Low IOPS
An SSD persistent disk is priced several times higher per gigabyte than standard, and that premium buys IOPS the workload is not issuing.
Free to start. No card. The playground just needs your work email.
Google Cloud
Found, explained, handed over.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across Google Cloud, with read-only access to the account.
Explain
Every finding says exactly what to change: Change the persistent disk type. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Persistent Disks on Google Cloud
- The fix, by hand
- Open Cloud Console → Compute Engine → Snapshots → CREATE SNAPSHOT from the resource.
- Stop the attached VM (Compute Engine → VM instances → STOP).
- Open Disks → CREATE DISK from the snapshot, picking the target type (pd-balanced / pd-ssd).
- Detach the old disk, attach the new one to the VM, and start the VM.
These are the steps the finding carries in the product.
- Category
- Rightsizing. Resources sized for headroom they never use. A smaller size runs the same workload for less.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1234- Full reference
Related checks
See the oversized resources 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.