-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Improve Inherited Context Lookup in getConfigResources #11048
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
base: main
Are you sure you want to change the base?
Conversation
good initiative @he1l0world , let’s wait till we have #11042 merged with further work on this one. It would be interesting to see if any positive performance impact is given on startup, by this change. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #11048 +/- ##
=========================================
Coverage 16.57% 16.57%
- Complexity 13967 13968 +1
=========================================
Files 5743 5743
Lines 510468 510476 +8
Branches 62073 62073
=========================================
+ Hits 84616 84623 +7
- Misses 416390 416391 +1
Partials 9462 9462
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Sure! |
Description
This PR improves the performance and clarity of the
getConfigResources
method in theModuleDefinitionSet
class.Previously,
getConfigResources
traversed the entire module hierarchy on each call, redundantly re-computing inherited context resources from parent modules. This change introduces memoization using a configResourcesMap. The result is a more efficient and maintainable implementation, especially as the number of modules grows.The work builds upon PR #11042, which added unit test coverage for this method. With tests in place, this change now optimizes the implementation while maintaining the same expected behavior.
I’m submitting this PR in draft form to:
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
Verified using the unit tests introduced in PR #11042
How did you try to break this feature and the system with this change?
Verified that duplicate traversal across inherited modules no longer occurs