Share via

Configure the compute size for a Databricks app

Important

This feature is in Beta.

Each Databricks app runs on compute resources that determine its processing power and memory. Choose a compute size when you create or edit an app to match your workload requirements.

Available compute sizes

The following compute sizes are available for Databricks apps:

Size CPU Memory Cost per hour When to use
Medium Up to 2 vCPUs 6 GB 0.5 DBU Standard apps with moderate resource needs, such as dashboards, simple data visualizations, and forms. Most apps work well with this size.
Large Up to 4 vCPUs 12 GB 1 DBU Apps that process large datasets in memory, handle high concurrency, or perform more intensive computations.

If you don't specify a compute size, Azure Databricks assigns the Medium size by default.

Configure compute size

Configure the compute size when you create or edit an app.

Create app

To set the compute size when you create a new app:

  1. Click compute icon Compute in the sidebar.
  2. Go to the Apps tab.
  3. Click Create app.
  4. In the Configure step, select a Compute size from the dropdown.
  5. Complete the remaining configuration steps and click Create app.

Edit app

To change the compute size for an existing app:

  1. Click compute icon Compute in the sidebar.
  2. Go to the Apps tab and click the app name.
  3. Click Edit
  4. In the Configure step, select a different Compute size from the dropdown.
  5. Click Save.

After you change the compute size, the app continues to run on the previous compute size until the update to the new compute size finishes. After the update finishes, the app switches over to the new size.

View the current compute size for an app on the Overview tab.

Best practices for compute sizing

When you choose a compute size for your app, consider the following best practices:

  • Most apps work well with the default Medium size. Only choose Large if you encounter performance issues or know your app has high resource requirements.
  • Test your app with the selected compute size in a development or staging workspace before you deploy it to production.
  • Consider cost implications. The Large compute size costs more per hour.