[android] cache Join
and Cap
enum values
#24248
Merged
+20
−26
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.
Context: #23991
Context: https://github.com/chabiss/periodictable
In the above sample, a lot of time is spent in:
This exposes a performance issue with
Java.Lang.Enum
values:java.lang.Enum
in Java are objects (notint
like C#)When accessing an enum value, Java returns an object we have to wrap in a C# object.
.NET for Android has to do bookkeeping around this, lookup in a hash table, etc.
To avoid this, we can store the
Join
andCap
values in a static field and avoid calling into Java. This approach is already working in .NET MAUI forImageView.ScaleType
:maui/src/Core/src/Platform/Android/AspectExtensions.cs
Lines 7 to 10 in 9361f90
After this change, the time spent is completely gone:
I can't find the same call for (the unfortunately named)
get_Butt()
at all.In the future, we might consider changing the C# binding for
Java.Lang.Enum
to "auto-cache" values in C# static fields. Not sure if there is enough time left for it to happen in .NET 9, though.