fix: TensorFlow memory and performance fixes #26
Merged
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
bjschoenfeld
approved these changes
Jul 31, 2024
jfilling
approved these changes
Jul 31, 2024
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.
When running BuildingSimulation benchmarks, I observed a very high amount of memory usage (MacBook Pro, M1 Max, 32GB RAM) during high-timestep simulations using TensorFlow. Some cases (100,000 timestep, single trial) failed to complete, with warnings thrown from TF about 'large unrolled loops'. TF documentation suggested using TensorFlow's control flow:
tf.range. To keep each trial isolated and independent, I'm keeping the trials'rangeusage as Python's.The observed effect of these two changes is that overall memory usage is reduced, lowering RAM hardware requirements, and performance is increased by decorating the
getGradientfunction with@tf.function. This decoration is recommended to avoid eager execution, and is a basic and straightforward measure to increase performance.