Photon Not Enabled
Queries run on the slower engine, so the same job holds the cluster for longer and is billed for that extra time.
Free to start. No card. The playground just needs your work email.
AWSAzureGoogle CloudDatabricks
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 AWS, Azure and Google Cloud, with read-only access to the account.
Explain
Every finding says exactly what to change: Enable the Photon engine on the cluster.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Databricks Cluster on AWS, Databricks Cluster on Azure, Databricks Cluster on Google Cloud
- The fix, by hand on AWS
- Enable Photon acceleration in the cluster runtime configuration.
- Benchmark DBU consumption before broad rollout.
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 IDs
RC-2211RC-2311RC-2411- 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.