[XLA:CPU] Release memory after compilation in HLO benchmarks.#44230
Open
copybara-service[bot] wants to merge 1 commit into
Open
[XLA:CPU] Release memory after compilation in HLO benchmarks.#44230copybara-service[bot] wants to merge 1 commit into
copybara-service[bot] wants to merge 1 commit into
Conversation
copybara-service
Bot
force-pushed
the
test_931186564
branch
5 times, most recently
from
ff6d734 to
2ab29f4
Compare
Compiling HLOs can use a significant amount of memory. To avoid OOMs when running benchmarks with many iterations, this change releases the memory associated with the compiled executable and purges per-thread caches to the OS after each compilation, outside of the timed benchmark loop. PiperOrigin-RevId: 931186564
copybara-service
Bot
force-pushed
the
test_931186564
branch
from
2ab29f4 to
5b2b814
Compare
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
1 participant
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.
[XLA:CPU] Release memory after compilation in HLO benchmarks.
Compiling HLOs can use a significant amount of memory. To avoid OOMs when running benchmarks with many iterations, this change releases the memory associated with the compiled executable and purges per-thread caches to the OS after each compilation, outside of the timed benchmark loop.