cancel
Showing results forย 
Search instead forย 
Did you mean:ย 
Administration & Architecture
Explore discussions on Databricks administration, deployment strategies, and architectural best practices. Connect with administrators and architects to optimize your Databricks environment for performance, scalability, and security.
cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

Managerment resource computer

AnhPT
New Contributor III

hi folks,

i'd like to gather some insights on how your teams manage compute policies in production environments.

Could you share:

  • How many compute policies you currently maintain?
  • How you categorize them (e.g., shared clusters, job clusters, interactive workloads, ETL, ML, etc.)?
  • Any best practices or lessons learned regarding policy governance and maintenance?

Thanks in advance for any suggestions or examples you can share.

1 REPLY 1

david85burger
Visitor

Most enterprise Databricks teams maintain 3 to 6 core compute policies in production, categorized by workload type: Interactive/Shared (multi-tenant all-purpose clusters for analysts), Job/ETL (cost-optimized automated job clusters enforcing Photon, spot instances, and worker limits), and ML/Analytics (GPU and single-node options). Key best practices include managing policies as code via Terraform or Databricks Asset Bundles (DABs), mandating tagging for cost attribution, enforcing aggressive auto-termination (20โ€“30 minutes) on interactive clusters, restricting high-cost instance types, and leveraging Serverless Compute wherever possible to minimize cluster management overhead.