-
Notifications
You must be signed in to change notification settings - Fork 321
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
Add the Asynchronous Dataloader #127
Add the Asynchronous Dataloader #127
Conversation
…g PR across. Sorry it's been a while
Hello @HenryJia! Thanks for updating this PR. There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻 Comment last updated at 2020-07-26 20:10:09 UTC |
Codecov Report
@@ Coverage Diff @@
## master #127 +/- ##
==========================================
- Coverage 92.25% 91.38% -0.88%
==========================================
Files 79 80 +1
Lines 4031 4084 +53
==========================================
+ Hits 3719 3732 +13
- Misses 312 352 +40
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
@HenryJia nice. Mind fixing the coverage? |
@williamFalcon Not entirely sure how to do that. The test requires a GPU to run since the dataloader needs a GPU (since to(device, non_blocking=True) requires device to be GPU), and I don't think any of the CI tests run on GPU machines? |
@Borda can we also add a set of GPUs for bolts? Ok, we’ll merge now and make sure to add the gpus here as well |
@HenryJia |
@williamFalcon |
yes. that’s not clear from the docs right now |
Firstly, really sorry it's been this long. I've finally got round all my uni stuff and graduated and actually have time now.
Before submitting
What does this PR do?
Add the asynchronous dataloader as discussed in
Lightning-AI/pytorch-lightning#1521
Lightning-AI/pytorch-lightning#1454
Lightning-AI/pytorch-lightning#1404
Lightning-AI/pytorch-lightning#1316
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Yes I had fun coding :)