Repository navigation
perf(android): create wrappers on the class prototype without a JSObject construction - #126
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.
A wrapper for a returned Java object was built by constructing a
JSObjectthrough its constructor callback, then setting an ownconstructorproperty and the class prototype on it. The class prototype already carries both the runtime marker andconstructor, so the wrapper is now a plain object created directly with that prototype: no construction through the engine's callback path and no extra own property. This is the same change in the Node-API and the direct runtime (MetadataNode::CreateJSWrapper).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.The direct runtime is 10–14% faster on the rows that create a wrapper. Node-API is flat, within noise: there the construction was not the dominant cost.
Return thisreturns an existing wrapper and does not reach this code.All cases
Only V8 was built and run.