-
Notifications
You must be signed in to change notification settings - Fork 68
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
mlos_bench: Trial repetition #756
Comments
Chatted about this, there is some confusion over some storage entries, but they aren't running concurrently (yet). We should
|
@motus I don't think all of this is handled yet, so reopening. |
…r to skip trials (microsoft#775) Solution: truncate microseconds of the current timestamp when scheduling new trials to be executed ASAP Closes microsoft#756
@eujing can you see if trial repeat with master is still broken? I observed it acts like a minimum bound and not as a maximum |
@yshady trial repeat seems to be working at an exact value when using the main branch. I have been using 1, and getting new configs proposed every time. Maybe this is not an issue anymore in the main branch. |
I was using 5 or more |
Should probably just write a test for this. |
I would like to run each config 30 times but not 30 at same time. For example, a default config should be running 30 times but not concurrently.
Currently trial repeat param for mlos_bench will run the trial repeat number all at the same ts_start
The text was updated successfully, but these errors were encountered: