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.
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
Implement a new, experimental variant of LookupResources as LookupResources2 #1905
Implement a new, experimental variant of LookupResources as LookupResources2 #1905
Changes from 4 commits
75ad751
f2c40f4
dedb1f8
5147ba1
d889495
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Initializing
syntheticResult.contextValues
with an empty map does an unnecessary allocation to the heap.combineMap
does take care of nil first argument when merging what has been found, which adds one extra unnecessary allocation.I did some benchmarks, and
combineMaps
can be made faster and do one less allocation in the case one of the arguments is nil or empty.Given the caveat is being executed for each one of the tuples coming out of
ReverseQueryRelationships
viaredispatchOrReportOverDatabaseQuery
, I thought this could lead to N unnecessary allocations in the critical path.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.
No need to clone them if they aren't changing
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.
please write a benchmark like I did, and make sure it reduces allocations and CPU time for:
My code above moved the needle from 3 allocations to 2 and made it 50% faster
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.
Since I don't clone now at all unless necessary, it should be 1 less even
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.
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't; the type of the result is not a synthetic
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.
Then: