fix: cpu memory savings of sharded dataloader #83
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Feb 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR brings back the cpu memory savings from sharded dataloading (#76). At 9km, the max cpu memory usage goes down from ~70% to ~30%.
The sharded reading clashed with the recent changes to Support masking of unconnected nodes (LAM). Since anemoi-datasets currently doesn't support slicing and indexing in one operation like
x = self.data[start : end : self.timeincrement, :, :, grid_shard_indices]the new version checks for the type of
grid_shard_indicesand does it in 2 steps if necessary.@Rilwan-Adewoyin @JPXKQX @b8raoult @floriankrb