Bug 276127
| Summary: | [run-benchmark] Add motionmark1.3 plan variant that enforces 15fps for low-end devices | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Nikolas Zimmermann <zimmermann> |
| Component: | Tools / Tests | Assignee: | Carlos Alberto Lopez Perez <clopez> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | clopez, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=276629 | ||
Nikolas Zimmermann
Add a MotionMark 1.3 run-benchmark plan variant that enforces 30FPS, to be used for low-power devices.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Nikolas Zimmermann
Pull request: https://github.com/WebKit/WebKit/pull/30392
Nikolas Zimmermann
Wrong approach, that needs to be revisited.
Carlos Alberto Lopez Perez
I have been testing this with Nikolas and it seems that 30FPS is still too much to get useful results on the RPi4 boards for performance regression tracking that we have at https://build.webkit.org/#/builders/895 and https://build.webkit.org/#/builders/892
With 30FPS the motionmark scores on the RPi4 are around 1-6 points and that is not useful for tracking regressions, also the animations on the screen are very poor, almost no complexity.
With 15FPS however the scores are around 100-600 and the animations on the screen look much better, you can clear see more complexity in the animations even when you can see that that it animates with low FPS.
Carlos Alberto Lopez Perez
Pull request: https://github.com/WebKit/WebKit/pull/30458
EWS
Committed 280660@main (9a083c67ec38): <https://commits.webkit.org/280660@main>
Reviewed commits have been landed. Closing PR #30458 and removing active labels.
Radar WebKit Bug Importer
<rdar://problem/131106556>