You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/advanced_usage/9_parallelism.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
# Parallelism
2
2
3
3
To facilitate fast execution, SMAC supports executing multiple workers simultaneously via [Dask](https://www.dask.org/). Using this functionality, splits SMAC into a main, and executor jobs.
4
-
The main job handles the Optimization Process, and coordination. The executors are queried with the target function and hyperparameter configurations, execute them, and return their result.
4
+
The main job handles the optimization process, and coordinates the executor jobs. The executors are queried with the target function and hyperparameter configurations, execute them, and return their result.
To utilize this split of main and execution jobs on a [SLURM](https://slurm.schedmd.com/), ``SMAC`` supports manually specifying a [Dask](https://www.dask.org/) client.
27
-
For example, this allows using independent jobs for execution, not necessarily running on the same machine/with identical hardware requirements as the main job.
26
+
To utilize this split of main and execution jobs on a [SLURM cluster](https://slurm.schedmd.com/), SMAC supports manually specifying a [Dask](https://www.dask.org/) client.
27
+
This allows executing the target function on dedicated SLURM jobs that are necessarily configured with the same hardware requirements,.
28
28
29
29
!!! note
30
30
31
-
While most ``SLURM`` clusters behave similarly, the example ``DASK`` client, might not work for every cluster. For example, some clusters only allow spawning new jobs
31
+
While most SLURM clusters behave similarly, the example DASK client, might not work for every cluster. For example, some clusters only allow spawning new jobs
32
32
from the login node.
33
33
34
34
To configure SMAC properly for each cluster, you need to know the ports which allow communication between main and worker jobs. The dask client is then created as follows:
0 commit comments