Replies: 2 comments 2 replies
|
2 years and that question never got answered, I can't imagine how much pressure PyTorch devs have to deny requests for such a looong period. |
0 replies
|
And yes, MultiEpochsDataLoader is amazing, and it shrinked a period of three days for my model to finish training, to 6 hours, by using 8 workers only, Imagine if I added more, It's very weird why such and amazing and polished library like PyTorch turned their gaze over such a critical problem, I can't imagine they was respawning all workers and reinitializing datasets in them for every iteration, this is unbelievable how they left it like that. |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hey everyone,
I've reused the MultiEpochsDataLoader because the normal Dataloader slows down after every epoch and it works just as desired.
Is there any reason why this isn't a standard Pytorch class? are there any Problems with type of dataloading?
Best greetings,
Filos
All reactions