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

[Feature] Make advance dataloader optional in iterbased training loop #1633

Open
jnoat92 opened this issue Feb 7, 2025 · 0 comments
Open

Comments

@jnoat92
Copy link

jnoat92 commented Feb 7, 2025

What is the feature?

Sometimes is not necessary to iterate the dataloader when resuming, mostly when the training batch is randomly sampled with replacement. Also, When working in the cloud, GPUs are reserved without being actually used during the advance dataloader iteration, which jeopardizes the management of resources.
It would be nice to make this step optional. Can we add an argument to the cfg options to skip this step?

Hope this request is useful.

Any other context?

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant