[CoreCLR] Cache JNI to Managed type mappings #10170
Merged
Conversation
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
Member
Author
|
/cc @grendello |
grendello
requested changes
Jun 4, 2025
Member
Author
|
@grendello PTAL |
grendello
approved these changes
Jun 4, 2025
jonathanpeppers
approved these changes
Jun 4, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I noticed there were thousands of log messages such as
I monodroid: Loaded type: Java.Lang.Objectprinted in logcat while running unit tests. It turns out we aren't caching the resolved type mappings when theGetJavaToManagedTypemethod is called fromAndroidRuntime.GetTypesForSimpleReference. This hurts performance because the call toclr_typemap_java_to_managedis fairly expensive.This PR makes sure we're using the
TypeManagerMapDictionaries.JniToManagedcache in this codepath.