- Notifications
You must be signed in to change notification settings - Fork26.3k
[jit] Cache node operators to speed up optimization#24827
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Closed
Closed
Uh oh!
There was an error while loading.Please reload this page.
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
We already cache the node's schema, but alias analysis wants operators.This ends up being almost 70% of the on-cpu time optimizing a largegraph.Here's some results on a [samplemodel](https://gist.github.com/suo/63ab9638516002176f94553a37060f61)(the units are seconds).Before:```compiled in: 20.256319999694824first run in: 313.77824568748474```After:```compiled in: 18.8815860748291first run in: 42.58739233016968```More than a 7x speedup! Still slower than I'd like though so I'll keepdigging.
suo added a commit that referenced this pull requestAug 19, 2019
We already cache the node's schema, but alias analysis wants operators.This ends up being almost 70% of the on-cpu time optimizing a largegraph.Here's some results on a [samplemodel](https://gist.github.com/suo/63ab9638516002176f94553a37060f61)(the units are seconds).Before:```compiled in: 20.256319999694824first run in: 313.77824568748474```After:```compiled in: 18.8815860748291first run in: 42.58739233016968```More than a 7x speedup! Still slower than I'd like though so I'll keepdigging.ghstack-source-id:4d524dcPull Requestresolved:#24827
MemberAuthor
suo commentedAug 19, 2019
cc@resistor for ongoing compiler optimization saga |
zdevito approved these changesAug 19, 2019
Contributor
facebook-github-bot commentedAug 19, 2019
Sign up for freeto 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.
Uh oh!
There was an error while loading.Please reload this page.
Stack fromghstack:
We already cache the node's schema, but alias analysis wants operators.
This ends up being almost 70% of the on-cpu time optimizing a large
graph.
Here's some results on asample model
(the units are seconds).
Before:
After:
More than a 7x speedup! Still slower than I'd like though so I'll keep
digging.
Differential Revision:D16887540