Repository navigation
perf(android): resolve primitive and String call sites without the overload matcher - #124
Open
ammarahm-ed wants to merge 1 commit into
Open
ammarahm-ed wants to merge 1 commit into
ammarahm-ed wants to merge 1 commit into
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the
|
This branch has not been deployed
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
Sign up for free
to 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.
MethodCallbackran the metadata-first overload match on every call, even for a method with one candidate: it parsed the signature into avector<string>, callednapi_typeofor inspected each argument, and built astd::vector<jclass>of parameter classes. For a method whose parameters are all primitives orString, none of that can change the outcome, so it is now resolved once per call site.On the first call,
MatchDirectSignatureturns the single candidate's signature into a string of parameter kinds (I,D,Z, ...,TforString) and caches it onMethodCallbackData. Each call then compares the argument types to that string and goes straight toCallJavaMethodwith the same match result the full matcher gave:nullorundefined: the entry is kept, not unambiguous;A signature with an object or array parameter, or a call that passes an object, array or function, still goes through the full matcher. Both the Node-API and the direct runtime get the change.
Results
V8 release build on a Sony SO-01M (Android 11, arm64), AOT-compiled with
cmd package compile -m speed. One warm-up launch is discarded, then 5 launches; values are the median ns per call.Rows this change does not touch moved by up to ±15% between runs (array and object returns by up to ±26%), which is this device's noise floor; only changes well beyond that are attributable.
All cases
Only V8 was built and run.