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

Dataloader cannot use num_workers>0L #78

Closed
cregouby opened this issue Jan 31, 2022 · 0 comments · Fixed by #83
Closed

Dataloader cannot use num_workers>0L #78

cregouby opened this issue Jan 31, 2022 · 0 comments · Fixed by #83
Labels
enhancement New feature or request

Comments

@cregouby
Copy link
Collaborator

as stated in #37 , Dataloader fail to run with num_workers>0L

Current behavior

When running with

#' @param num_workers (int, optional): how many subprocesses to use for data
, we get

# Error : callr subprocess failed: external pointer is not valid
# Run `rlang::last_error()` to see where the error occurred.
# De plus : Messages d'avis :
# 1: Datasets used with parallel dataloader (num_workers > 0) shouldn't have fields containing tensors as they can't be correctly passed to the wroker subprocesses.

Impact

The dataloader is currently a bottleneck in situation where the torch engine ( GPU ) is faster to process tensors than the dataloader ( single CPU core) to prepare it.

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

Successfully merging a pull request may close this issue.

1 participant