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 Dash apps, workspaces, and services (managed Redis or Postgres databases) can consume.
Viewing licensed memory usage and editing memory limits are administrator actions and require the admin role.
To view the current memory usage of the total combined Dash apps, workspaces, and services in Dash Enterprise, go to Platform and Users. The Memory Usage and Limits information displays the current usage in relation to your licensed memory limit.
<img>
Remember that available memory is calculated using licensed memory, and licensed memory excludes memory reserved for the core system. If you use a different tool to monitor memory on the system, you’ll see different information for available or maximum memory.
A warning banner is displayed in the App Manager when the memory usage reaches 80% of your licensed memory limit. When this banner appears, 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, Dash app developers are unable to initialize new apps, create new workspaces, or add new services.
To see the memory usage of a specific app, go to its App Info and select the Scale tab. The Memory Usage information displays the current memory usage for the app’s combined processes and workspace (memory usage for services is not shown).
<img>
To drill down further and see memory usage for each specific app, workspace, and service on Dash Enterprise, you can run kubectl commands against the Kubernetes cluster.
To view the memory usage of all apps and workspaces in the cluster:
kubectl top pods -n dash-apps
The output is similar to:
NAME CPU(cores) MEMORY(bytes)
quarterly-results-----web-7dfcfhd5b7-l2xpw 9m 104Mi
sales-analysis-----web-78bf6cj6f5-tg8hs 9m 821Mi
workspace-quarterly-results-668c6b4167-h8cxp 3m 305Mi
workspace-sales-analysis-7498960d4c-6k4w2 3m 241Mi
The NAME column contains the names of the pods that are responsible for app processes and workspaces. Names in the format <app-name>-----<process>-<ID> represent app process pods, and those in the format workspace-<app-name>-<ID> represent workspace pods. Divide the number in the MEMORY(bytes) column by 1024 to obtain the current memory usage in GiB.
To view the memory usage of all services in the cluster:
kubectl top pods -n dash-services
The output is similar to:
NAME CPU(cores) MEMORY(bytes)
postgres-quarterly-results-0 3m 112Mi
redis-sales-analysis-0 3m 111Mi
The NAME column contains the names of the pods that are responsible for the managed databases. Names in the format postgres-<app-name>-0 represent Postgres database pods, and those in the format redis-<app-name>-0 represent Redis database pods.
Divide the number in the MEMORY(bytes) column by 1024 to obtain the current memory usage in GiB.
You can use memory usage information to help inform decisions around memory limits.
To manage memory limits, you can:
Known limitation: Services don’t inherit the default memory limit.
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 Dash app processes, workspaces, and services to a maximum of 24 GiB (each node in the Kubernetes cluster has 32 GiB but 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.
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: