276127 2024-07-02 08:52:16 -0700 [run-benchmark] Add motionmark1.3 plan variant that enforces 15fps for low-end devices 2024-07-15 15:12:35 -0700 1 1 1 Unclassified WebKit Tools / Tests WebKit Nightly Build Unspecified Unspecified RESOLVED FIXED https://bugs.webkit.org/show_bug.cgi?id=276629 InRadar P2 Normal --- 1 zimmermann clopez clopez webkit-bug-importer oldest_to_newest 2044204 0 zimmermann 2024-07-02 08:52:16 -0700 Add a MotionMark 1.3 run-benchmark plan variant that enforces 30FPS, to be used for low-power devices. 2044205 1 zimmermann 2024-07-02 08:54:36 -0700 Pull request: https://github.com/WebKit/WebKit/pull/30392 2044423 2 zimmermann 2024-07-03 04:41:44 -0700 Wrong approach, that needs to be revisited. 2044519 3 clopez 2024-07-03 13:05:16 -0700 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. 2044529 4 clopez 2024-07-03 13:29:47 -0700 Pull request: https://github.com/WebKit/WebKit/pull/30458 2044645 5 ews-feeder 2024-07-04 00:52:08 -0700 Committed 280660@main (9a083c67ec38): <https://commits.webkit.org/280660@main> Reviewed commits have been landed. Closing PR #30458 and removing active labels. 2044646 6 webkit-bug-importer 2024-07-04 00:53:14 -0700 <rdar://problem/131106556>