perf(core): optimize context switching with lazy caching #16320
Closed
+44
−14
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
The
switchToHttp(),switchToRpc(), andswitchToWs()methods inExecutionContextHostcreate a new proxy object viaObject.assign()on every invocation.Problem:
ExecutionContextinstance is reused across guards/interceptors, causing multipleswitchToHttp()callsObject.assign()calls per requestIssue Number: N/A
What is the new behavior?
Lazy caching pattern:
switchToHttp(),switchToRpc(),switchToWs()Performance improvements:
Object.assign()callsSafety:
readonlyreference, closures evaluate at call-time)Testing:
switchTo*methodDoes this PR introduce a breaking change?
Other information
Implementation:
httpCache,rpcCache,wsCache)thisand evaluategetArgByIndex()at runtimeImpact: