Reduce performance impact of compiler.enable decorator #7498
Conversation
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
Signed-off-by: Max Kovalenko <[email protected]>
sfc-gh-truwase
approved these changes
Aug 18, 2025
LYMDLUT
pushed a commit
to LYMDLUT/DeepSpeed
that referenced
this pull request
Aug 20, 2025
) For some accelerators (such as HPU) running in a non-compile scenarios, the `compiler.enable` decorator can cause significant performance drops up to 8-12%. We can easily avoid the performance hit in non-compile scenarios, by detecting the ongoing compilation and returning immediately. Signed-off-by: Max Kovalenko <[email protected]> Co-authored-by: Olatunji Ruwase <[email protected]> Signed-off-by: lym <[email protected]>
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.
For some accelerators (such as HPU) running in a non-compile scenarios, the
compiler.enabledecorator can cause significant performance drops up to 8-12%.We can easily avoid the performance hit in non-compile scenarios, by detecting the ongoing compilation and returning immediately.