-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
core(mpfid): add list of loaf durations to debugdata #15685
Conversation
@@ -92,6 +108,7 @@ class MaxPotentialFID extends Audit { | |||
type: 'debugdata', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We won't see the observedLoafs
if they were all below FCP in this case. The function will still return undefined because there is no max duration/blocking events after FCP.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Good catch
}); | ||
if (loafEvents.length === 0) return; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This case won't really hurt anything without this check, so is mostly for aesthetics (prevent empty {type: 'debugdata', observedLoafs: []}
hanging around in LHRs)
Building on #15684, also logs LoAF startTime/durations in mpfid debugdata to be able to evaluate if a windowed function over LoAFs (e.g. max sum of LoAF blockingDurations in a 5s window) would be useful.
No visible changes. Again the intended purpose is analysis via a source like HTTP Archive.
I also didn't realize how "minimal" "Tests are minimal" was in #15684 because I forgot to add the unit test file to the commit. Whoops! Added in this PR.