Clarifications about RAM usages under different ordering options#79
Merged
GuillaumeLeclerc merged 6 commits intolibffcv:mainfrom Jan 22, 2022
Merged
Conversation
Collaborator
|
It looks great thank you very much for the contribution! |
Contributor
Author
|
Thank you for this great project and your active communication with users! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Added clarification note in the Dataset ordering section, explaining how each ordering option affects the amount of RAM needed.
Added a sentence in Scenario: large scale dataset to clarify
RANDOMoption is not feasible even os_cache is set False.