Repository navigation
perf(android): cache the thread's JNIEnv instead of calling GetEnv per JEnv - #123
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 Java call builds several
JEnvobjects on its way through the bridge, and each one calledJavaVM::GetEnv.JEnvnow reads the thread'sJNIEnvfrom athread_localand only asks the VM when none is set. Both the Node-API and the direct runtime get the change; it is the design from NativeScript/android#2092.A
JNIEnvis only valid while its thread stays attached, so the cache is set only where that lifetime is known:Runtime::Initpins the env untilDestroyRuntime. A worker thread also unpins it right beforeDetachCurrentThread.initNativeScript,runModule,runScript,callJSMethodNativeandcreateJSInstanceNativehold the env they were given in anEntryScopefor the length of the call and then restore the previous value. A pinned env is left alone.GetEnvSlowattaches is never cached, because nothing would tell us when it goes stale.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 gain is a few percent per call, close to this device's run-to-run noise on single rows (about ±5% on primitive calls), so read the pattern across rows rather than any one cell.
All cases
Only V8 was built and run.