Memory Limits

This documentation is for Dash Enterprise.
Dash Enterprise is the fastest way to write & deploy Dash apps and
Jupyter notebooks.
10% of the Fortune 500 uses Dash Enterprise to productionize AI and
data science apps. Find out if your company is using Dash Enterprise.

Dash Enterprise licenses have a memory limit. This limit represents the maximum amount of memory that total combined apps, workspaces, and services (managed Redis or Postgres databases) can consume.

To control the amount of licensed memory that resources on Dash Enterprise can consume, you can manage limits in Dash Enterprise. Managing memory limits is an administrator action and requires the admin role.

Managing Memory Limits

To manage memory limits, you can:

• Adjust the default memory limit that is applied to app processes and workspaces. It is set to 8 GiB (8,192 MiB) by default, but can be anywhere between 0.25 GiB and 10 GiB.

  Known limitation: Services don’t inherit the default memory limit.

• Set custom memory limits on specific app processes, workspaces, and services.

You can use memory usage information to help inform decisions about memory limits.

When an app reaches its memory limit, replicas. When a workspace reaches its memory limit (usually because the development app is running), the development app is stopped and killed is printed in the workspace terminal.

Changing the Default Memory Limit

Changing the default memory limit has no effect on app processes and workspaces that have custom memory limits.

To change the default memory limit:

1. In the App Manager, go to Platform and Users. Remember that you need the admin role to be able to access platform and user information.
2. In Memory Usage and Limits, select Edit Memory Limits.
3. In Default Limits (GiB)s, enter the new default limit.
4. Select Save.

New apps and workspaces will inherit the updated default memory limit. To apply the updated default limit to an existing app process that doesn’t have a custom limit, restart the process from the Overview tab in the App Info. To apply the updated default limit to an existing workspace that doesn’t have a custom limit, restart or rebuild the workspace from the Workspace tab in the App Info.

Setting a Custom Memory Limit for an App Process, Workspace, or Service

It’s good practice to set limits that are appropriate for each resource. If your organization has deployed apps with a variety of memory usage levels and the default memory limit is not appropriate for all of them, consider setting custom memory limits.

You can set custom memory limits for app processes, workspaces, and services to a maximum of 24,576 MiB, or 24 GiB.

If your Dash Enterprise server has 24 GiB or less memory, setting a resource’s memory limit to 24 GiB gives it the ability to consume it all. Keep this in mind when configuring custom memory limits.

If a process has multiple scaling apps, the custom memory limit applies to each replica. It is not shared between replicas.

When you save a custom memory limit, the resource is restarted. In the case of a service, both the service and the workspace (if one is attached) are restarted.

To set a custom memory limit on an app process, workspace, or service:

1. In the App Manager, go to the App Info for the app whose process, workspace, or service you want to set a custom memory limit for.
2. Go to the Scale tab.
3. Find the process, workspace, or service whose memory limit you want to edit, and then select Edit Resources.
4. In Memory Limit, enter the new custom memory limit in MiB.
5. Select Save and Restart. The resource is restarted.

Nearing and Reaching the Licensed Memory Limit

When memory usage reaches 80% of your licensed memory limit, a warning banner is displayed in the App Manager and