Instance Pool Min-Idle Underutilised
Min-idle instances are held ready and billed so a cluster can start quickly; instances beyond what starts actually need are paying for readiness nothing uses.
Free to start. No card. The playground just needs your work email.
AWSAzureGoogle CloudDatabricks
Found, explained, handed over.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across AWS, Azure and Google Cloud, with read-only access to the account.
Explain
Every finding says exactly what to change: Reduce idle instances in the pool. 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
- Databricks Pool on AWS, Databricks Pool on Azure, Databricks Pool on Google Cloud
- The fix, by hand on AWS
- Lower 'Min Idle' toward 0 if warm-start latency is acceptable.
- Enable idle-instance auto-termination on the pool.
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 IDs
RC-2205RC-2305RC-2405- 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.