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

Memory Allocation? #1

Open
egrace479 opened this issue May 17, 2024 · 0 comments
Open

Memory Allocation? #1

egrace479 opened this issue May 17, 2024 · 0 comments
Labels
documentation Improvements or additions to documentation question Further information is requested

Comments

@egrace479
Copy link
Member

This downloader loads each batch into memory before writing the files to disk, since our initial storage plan was to use HDF5.
Since we decided to transfer the dataset into either HDF5 or webdataset format after completing the download to avoid data backup complications and difficulties with parallel data writes, this setup is open to change.

The question is whether it is worth changing to writing image data as it comes down to reduce the memory bottleneck and utilize cores more efficiently.

@egrace479 egrace479 added documentation Improvements or additions to documentation question Further information is requested labels May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant