Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LoAF: Amend blockingDuration to match implementation #127

Merged
merged 1 commit into from
Jan 15, 2024
Merged

Conversation

noamr
Copy link
Contributor

@noamr noamr commented Jan 11, 2024

blockingDuration is a total duration of all the blocking part (anything above the first 50ms) tasks that contributed to the LoAF. The rendering duration is considered as part of the longest task.


Preview | Diff

`blockingDuration` is a total duration of all the blocking part (anything above the first 50ms)
tasks that contributed to the LoAF. The rendering duration is considered as part of the longest
task.
@noamr noamr requested a review from mmocny January 11, 2024 14:07
@noamr
Copy link
Contributor Author

noamr commented Jan 11, 2024

@mmocny this is what we originally agreed about re blockingDuration and what's implemented.

Copy link
Contributor

@mmocny mmocny left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great, LGTM.

I think the one question I have is that the algorithm depends on the definition of update-the-rendering-start-time and at least from Chromium I know that there was some question about which work can or cannot sneak in. I suspect that is beyond scope for this since its really about the event loop / update-the-rendering steps themselves.

@noamr noamr merged commit 88193ec into main Jan 15, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants