Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Q] Prioritizing Runs in Grid Search Sweeps #7585

Open
itay-nakash opened this issue May 7, 2024 · 1 comment
Open

[Q] Prioritizing Runs in Grid Search Sweeps #7585

itay-nakash opened this issue May 7, 2024 · 1 comment
Labels
c:sweeps Component: Sweeps

Comments

@itay-nakash
Copy link

Hi everyone,

I'm using a sweep with grid search across several parameters, and each run is pretty time-consuming.
I would like to prioritize runs with certain hyperparameters, that are more urgent for my testing, modeling, and reports.
However, I can't find a convenient way to prioritize the runs, other than manually managing the agents by starting and stopping them until they hit the desired parameters, then cleaning up by deleting the killed runs to ensure they eventually get executed.

Is there a more elegant solution for prioritizing runs in a grid search? Or am I missing something?

If not, I would suggest adding a "priority" feature to grid search sweeps.
For instance, allowing users to specify the order of experiments or choose specific ones to prioritize, or perhaps a flag that could be added to the wandb agent lunching command to define the desired parameters for the first run.

Thanks for your help!

@wandb wandb deleted a comment from exalate-issue-sync bot May 8, 2024
@luisbergua
Copy link
Contributor

Hi @itay-nakash, thanks for sharing this helpful feedback! That's currently not possible but I'll be happy to submit a feature request internally for you

@kptkin kptkin added the c:sweeps Component: Sweeps label May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c:sweeps Component: Sweeps
Projects
None yet
Development

No branches or pull requests

3 participants