[Feature] Make advance dataloader optional in iterbased training loop #1633
Description
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