-
Notifications
You must be signed in to change notification settings - Fork 23
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
Better allocation of workers for train and validation sets #260
Labels
enhancement
New feature or request
Comments
hm to be honest I think my fix in #327 made it worse, will reopen |
lucidtronix
pushed a commit
that referenced
this issue
Jan 13, 2023
lucidtronix
pushed a commit
that referenced
this issue
Jan 13, 2023
lucidtronix
pushed a commit
that referenced
this issue
Jan 13, 2023
lucidtronix
pushed a commit
that referenced
this issue
Jan 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What
Allocate workers based on number of train vs. validation steps, so that the validation workers don't pull way ahead of the train workers.
Why
Better use of cpus for faster training.
How
num train workers = training steps / (training steps + validation steps) or something
Acceptance Criteria
Workers allocated based on number of train vs. validation steps.
Speed comparison would be good, ideally through a test!
The text was updated successfully, but these errors were encountered: