Send GFP (Good Frame Probability) on 200th frame.#7711
Merged
lannka merged 4 commits intoampproject:masterfrom Feb 22, 2017
Merged
Send GFP (Good Frame Probability) on 200th frame.#7711lannka merged 4 commits intoampproject:masterfrom
lannka merged 4 commits intoampproject:masterfrom
Conversation
cramforce
approved these changes
Feb 22, 2017
mrjoro
pushed a commit
to mrjoro/amphtml
that referenced
this pull request
Apr 28, 2017
* Send GFP on 200th frame. * Fix lint * fix test * fix type checks
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
2 participants
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.
As discussed, send on 200th frame is to normalize the number across page view. Since the first several frames is usually heavy. And once all content loaded, the browser turns into idle. 200 is a magic number that makes sure we're measuring same thing all the time.