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.
Editing memory limits is an administrator action and requires the admin role.
To manage memory limits, you can:
Known limitation: Services don’t inherit the default memory limit.
You can use memory usage information to help inform decisions about memory limits.
When an app reaches its memory limit, it is stopped. 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 has no effect on app processes and workspaces that have custom memory limits.
To change the default memory limit:
admin role to be able to access platform and user information.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.
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 GiB.
When Dash Enterprise is installed on a multi-node Kubernetes cluster, each node in the cluster typically has 32 GiB and approximately 8 GiB is reserved for the core system. If you set a resource’s memory limit to 24 GiB, this gives it the ability to consume all the available memory on the node that Kubernetes has scheduled it on. Similarly, when Dash Enterprise is installed on a single server, and that single 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 replicas, 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:
When memory usage reaches 80% of your licensed memory limit, a warning banner is displayed in the App Manager and scaling apps (including autoscaling) is disabled. We recommend pausing activity on Dash Enterprise until the memory usage is reduced or your licensed memory limit is increased. Contact us to increase your licensed memory limit.
When the licensed memory limit is reached, app developers are unable to initialize new apps, create new workspaces, or add new services.