-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Performance Robustness in Reverse Pass #442
Merged
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
Codecov ReportAttention: Patch coverage is
|
Performance Ratio:
|
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.
This PR contains some work to ensure that various
Ref
s inserted into the reverse-pass IR always get SROA'd away reliably. This is a PR in the same vein as #430 and #438 -- change how things are implemented to ensure that we're completely insensitive to what type inference / constant prop happens to let us do. The pay off for this kind of work is not receiving hard-to-debug issues in the future / users seeing poor performance, not telling us about it, and giving up on Mooncake entirely.In short, a variety of Julia functions are inserted into the reverse pass IR at them minute, whose calls must get inlined away if SROA is to successfully remove the
Ref
s. There are various reasons that Julia might not inline these calls away, for example if the argument types are not known statically (meaning that we get dynamic dispatch). This does not just affect functions whose performance we do not care about -- suppose a particular method instance is mostly type stable, but has one or two lines which are type-unstable and are rarely / if ever hit in practice. At present, the presence of these type instabilities will cause the reverse-pass of AD to have additional allocations.This PR will remove the possibility of this happening by removing these generic functions altogether and inserting the code to handle the references directly into the IR. i.e. you'll see various
getfield(ref, :x)
andsetfield!(ref, :x, val)
calls inserted directly.todo