[Android] Changes to improve Border control drawing performance #3620
Conversation
This file contains 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
jsuarezruiz
added
t/bug
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
hartez
approved these changes
Dec 3, 2021
|
@hartez With the second sample a big part of the time is with Layouts (OnLayout, OnMeasure). We can merge this PR, but, after that could we share some time reviewing what's happening at Layout level to try to improve more? |
Sure. |
Eilon
added
t/perf
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.
Description of Change
Changes to improve Border control drawing performance on Android. Changes:
And with other sample using virtualization.
(NOTE: Left emulator is using Preview 10, and the right one this branch)
PR Checklist
Does this PR touch anything that might affect accessibility?