Improvement on memory usage#282
Merged
ahmedfgad merged 1 commit intoahmedfgad:masterfrom Mar 27, 2024
Merged
Conversation
ahmedfgad
approved these changes
Mar 27, 2024
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.
I find the use of garbage collector usefull when using the pygad on colab, because when I tried to train some examples on standard version of quotas colab (12GB RAM), not PRO, the usage of memory exceeded the quantity available and so the colab restarted itself not allowing to train for more than 3 generations. With
gc.collect()used outside ofon_generationor inside was possible to release the memory and not crash.