Use the Dask Cluster Settings page to view preferences for the Dask cluster that backs the Covalent default executor. The Dask Cluster settings are not editable in the Covalent GUI, but can be configured as described in the Dask documentation. In most cases there is no need to adjust the Dask configuration used with Covalent.
If No Cluster is set to True in the SDK Settings page, then the Covalent server does not start the Dask cluster and instead uses the local executor by default.
- Cache Directory
The directory path that Dask uses for cacheing.
- Log Directory
The directory path of the Dask cluster logs.
- Mem Per Worker
The memory allocated per worker process. For larger workloads the default memory per worker for a local Dask cluster might be too small. See the Dask worker memory documentation for information about setting worker memory. (This is an exception to the rule that the default Dask settings are adequate for most cases.)
- Threads Per Worker
The number of threads allocated to each worker node in the Dask cluster.
- Num Workers
The number of workers in the Dask cluster.
- Scheduler Address
The IP address and port for the Dask scheduler.
- Dashboard Link
The URL of the Dask dashboard.
- Process Info
The name and parent process of the Dask cluster.
The main process ID of the Dask cluster. This is the parent of the Dask worker processes.
- Admin Host
The IP address of the Dask admin UI. For the default Dask cluster, this is the local host.
- Admin Port
The port of the Dask admin UI.