Skip to main content
A Databricks App bills for its compute the whole time it is running, whether or not anyone uses it. nOps finds apps that run almost all the time and estimates the saving from stopping them outside business hours.

Why it matters

Lab, demo and test apps are easy to start and easy to forget, and each keeps billing until someone stops it.

How nOps finds it

nOps reads the last 30 days of Databricks billing. A resource is flagged when it was billed in at least 90% of the hours of the last 30 days (or since your first Databricks day, if later), was still running on the last complete day, and sat at its minimum level (within 5% of its 10th-percentile hourly usage) in at least 80% of off-hours. Off-hours are weekends and weekday hours outside 13:00-24:00 UTC. The saving is what the app cost in those off-hours, scaled to 30 days, and must be at least $10 a month.

Before you start

Know who uses the app and whether anyone needs it outside business hours.

How to implement

  1. Check with the app’s owner whether it is still used, and when.
  2. If it is no longer needed, delete it in Databricks (Compute → Apps).
  3. Otherwise stop it outside business hours: stop it from the app page, or on a schedule with databricks apps stop APP_NAME and databricks apps start APP_NAME in a scheduled job.
  4. Check after a week that it no longer bills around the clock.

Risks and considerations

  • A stopped app is unavailable until it is started again, and starting takes a short time.
  • Deleting an app removes it; keep its source code so it can be redeployed.