Sometimes you want to run the same application with multiple different configurations.
E.g. running a performance test on each of the databases with each of the schemas.
-m) flag and pass a comma separated list specifying the values for each dimension you want to sweep.
The following sweeps over all combinations of the dbs and schemas.
[2021-01-20 17:25:03,317][HYDRA] Launching 6 jobs locally[2021-01-20 17:25:03,318][HYDRA] #0 : db=mysql schema=warehouse[2021-01-20 17:25:03,458][HYDRA] #1 : db=mysql schema=support[2021-01-20 17:25:03,602][HYDRA] #2 : db=mysql schema=school[2021-01-20 17:25:03,755][HYDRA] #3 : db=postgresql schema=warehouse[2021-01-20 17:25:03,895][HYDRA] #4 : db=postgresql schema=support[2021-01-20 17:25:04,040][HYDRA] #5 : db=postgresql schema=school
The printed configurations have been omitted for brevity.
You can also define sweeping in the input configs by overriding
hydra.sweeper.params. Using the above example, the same multirun could be achieved via the following config.
hydra: sweeper: params: db: mysql,postgresql schema: warehouse,support,school
The syntax are consistent for both input configs and commandline overrides. If a sweep is specified in both an input config and at the command line, then the commandline sweep will take precedence over the sweep defined in the input config. If we run the same application with the above input config and a new commandline override:
[2021-01-20 17:25:03,317][HYDRA] Launching 3 jobs locally[2021-01-20 17:25:03,318][HYDRA] #0 : db=mysql schema=warehouse[2021-01-20 17:25:03,458][HYDRA] #1 : db=mysql schema=support[2021-01-20 17:25:03,602][HYDRA] #2 : db=mysql schema=school
The above configuration methods only apply to Hydra's default
BasicSweeper for now. For other sweepers, please checkout the
Hydra supports other kinds of sweeps, e.g:
x=range(1,10) # 1-9schema=glob(*) # warehouse,support,schoolschema=glob(*,exclude=w*) # support,school
See the Extended Override syntax for details.
The default sweeping logic is built into Hydra. Additional sweepers are available as plugins. For example, the Ax Sweeper can automatically find the best parameter combination!
By default, Hydra runs your multi-run jobs locally and serially. Other launchers are available as plugins for launching in parallel and on different clusters. For example, the JobLib Launcher can execute the different parameter combinations in parallel on your local machine using multi-processing.