Repository navigation
perf(android): create ArrayBuffer.from without calling ByteBuffer.isDirect - #132
Open
ammarahm-ed wants to merge 2 commits into
Open
ammarahm-ed wants to merge 2 commits into
ammarahm-ed wants to merge 2 commits 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.
Port of NativeScript/android#2076 to both the Node-API and the direct runtime.
ArrayBuffer.from(byteBuffer)calledByteBuffer.isDirect()through JNI to choose between the zero-copy path and the copying path.GetDirectBufferAddressalready returns null for a heap buffer, so the null check now picks the path and the Java call, its cached method id and them_isDirectMethodIDfield are gone. A direct buffer whose address is unavailable falls back to the copying path, which works for both kinds.In the Node-API tree the
nativeObjectkey is now set withnapi_set_named_propertyinstead of creating a string value for it on every call. The upstream change also caches that key as av8::Eternal, which has no counterpart here, and the direct runtime already sets the property by name.The two new benchmark cases are in the first commit.
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.Only the direct-buffer rows go through the code this removes a JNI call from. The heap-buffer rows are within noise. The Node-API heap-buffer case is about 70 µs per call in both builds because its copying path makes several JNI calls; that is not changed here.
All cases
Only V8 was built and run. These numbers come from builds of this change on top of an earlier revision of the PR below it, which does not touch this code path.
The Jasmine suite on a debug build of this branch, same device: Node-API 522 specs, 0 failures; direct 450 specs, 0 failures (main: 523 and 0; 451 and 1 failure in a timing spec).