Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: de6e87fb4c3cce308f3326c57a2cb528241c454f
https://github.com/WebKit/WebKit/commit/de6e87fb4c3cce308f3326c57a2cb528241c454f
Author: Nikolas Zimmermann <nzimmerm...@igalia.com>
Date: 2024-09-24 (Tue, 24 Sep 2024)
Changed paths:
A
Tools/Scripts/webkitpy/benchmark_runner/data/patches/extra/MotionMark1.3.1-15FPS.patch
A
Tools/Scripts/webkitpy/benchmark_runner/data/patches/extra/MotionMark1.3.1-60FPS.patch
A
Tools/Scripts/webkitpy/benchmark_runner/data/plans/motionmark1.3.1-15fps.plan
A
Tools/Scripts/webkitpy/benchmark_runner/data/plans/motionmark1.3.1-60fps.plan
Log Message:
-----------
[WPE] Upgrade our custom run-benchmark plans to use MotionMark 1.3.1
https://bugs.webkit.org/show_bug.cgi?id=280051
Reviewed by Simon Fraser and Carlos Garcia Campos.
Switch our custom run-benchmark plans to use MotionMark 1.3.1.
This has the main benefit that we can run individual subtests,
and get the right 'canvas size', which is one of the 1.3.1
fixes.
Furthermore rework the 15 FPS logic, to unbreak score computation.
The expectation is that the cadence of the rAF() callback matches the
screen refresh rate -- however we still want to run at 60 Hz refresh
rate, but artifically limit the complexity, to get higher scores on
embedded devices (e.g. a few hundred points, instead of scores between
1-4 depending on the subtest). This increases the likelihood to detect
regressions/progresses, even on low-end devices.
Realize this by injecting a rAF() proxy, which only calls the MotionMark
rAF() logic, every 4th callback, simulating 15 FPS.
*
Tools/Scripts/webkitpy/benchmark_runner/data/patches/extra/MotionMark1.3.1-15FPS.patch:
Added.
*
Tools/Scripts/webkitpy/benchmark_runner/data/patches/extra/MotionMark1.3.1-60FPS.patch:
Added.
*
Tools/Scripts/webkitpy/benchmark_runner/data/plans/motionmark1.3.1-15fps.plan:
Added.
*
Tools/Scripts/webkitpy/benchmark_runner/data/plans/motionmark1.3.1-60fps.plan:
Added.
Canonical link: https://commits.webkit.org/284147@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
_______________________________________________
webkit-changes mailing list
webkit-changes@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-changes
