-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[mono][interp] Add max limit to the imported IL when inlining #121580
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
Open
BrzVlad
wants to merge
1
commit into
dotnet:main
Choose a base branch
from
BrzVlad:fix-interp-inline-budget
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+11
−0
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you check with the JIT team if they have a similar limit (I would expect so) and maybe we could put a similar value here.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe the jit has a more complex approach to inlining budget. From a quick look through the code they do a rough estimation based on the initial code size, then they have the max allowed increased in compilation time defined here https://github.com/dotnet/runtime/blob/main/src/coreclr/jit/compiler.h#L11281, and for each method to inline they add the cost via this estimation https://github.com/dotnet/runtime/blob/main/src/coreclr/jit/inline.cpp#L1097. (cc @AndyAyersMS in case I'm saying something wrong).
I didn't want to overly engineer this, since I'm not sure it is worth investing time into it, also risking some potential regressions. Also those numbers might be more specific to the RyuJIT and not apply ideally to the mono interpreter. This was just a simple and safe fix to prevent outliers that could prove problematic in production.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great - I agree that if the mechanism is not comparable, then let's stick with your value (the reasoning for it good)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think the RyuJit heuristic would generalize well ... also we are not super happy with it as it tends to give up on inlining too soon. What @BrzVlad proposes here looks sensible.