Repository navigation
Conversation
Author
|
Hi, hope this change fulfills the contributing requirements - happy to discuss! :) |
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.
What
Makes the Android memory read run on its own background
HandlerThreadinstead of the main looperWhy
On Android, the toolkit reads
/proc/<pid>/smaps_rollupevery 500ms (HybridPerformanceToolkit.collectUsedRam), and it did so on the main looper. While testing on a physical device (Realme 6), each read took about 57ms of UI-thread CPU, which equated to roughly 5 dropped frames when it landed during a scroll or animation. Moving the sampling to a background thread reduced the idle UI-thread CPU usage