RUM-8627: Collect App Hitches in the SDK #2214
Open
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 and why?
This PR creates the engine to collect View Hitches (Slow frames) that occur during the lifecycle of a View.
The proposed solution is defined in the internal RFC.
How?
To scale the entities that observe the render loop, it was created the
DisplayLinker
.Any reader (
RenderLoopReader
) that wants to be notified about frame rendering can register to theDisplayLinker
:displayLinker.register(vitalRefreshRateReader)
This PR lists two
RenderLoopReader
:VitalRefreshRateReader
- A class that reads the refresh rate (frames per second)ViewHitchesReader
- A class that reads View Hitches or Slow frames.For a better understanding of the relationships, the figure below depicts the idea:

Review checklist
make api-surface
)