Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
MotionMark scores are super sensitive to a single long frame
https://bugs.webkit.org/show_bug.cgi?id=220847 <rdar://problem/74152743> Reviewed by Maciej Stachowiak and Jon Lee. Currently, "ramp" tests have three phases. The middle phase is where they try to determine a maximum reasonable complexity, and the third one is where they try various complexities between 0 and the maximum. The calculation of this maximum reasonable complexity is currently very sensitive to outlier frame times. If there is a single outlier frame time, the failure mode is to assume that the maximum complexity is ~10. So, the solution is to ignore outlier frame times during this first phase, and to ensure that there are at least 9 frames measured that have non-outlier times. * MotionMark/tests/resources/main.js: (filterOutOutliers): (_measureAndResetInterval): (update): (registerFrameTime): (intervalHasConcluded): (start): (didFinishInterval): Canonical link: https://commits.webkit.org/234319@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@273122 268f45cc-cd09-0410-ab3c-d52691b4dbfc
- Loading branch information
Showing
2 changed files
with
83 additions
and
10 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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