MotionMark's multiply suite may generate incorrect score when requestAnimationFrame runs at 120hz

smfr · smfr · commit f5d127cff37d · 2023-08-14T15:32:00.000-07:00
https://bugs.webkit.org/show_bug.cgi?id=240605 Reviewed by Simon Fraser. This effectively increases the maximum complexity. Doing this for two reasons: both Chrome and Safari are getting close to the maximum complexity. Increasing the complexity ensures Chrome is scored correctly when requestAnimationFrame runs at 120Hz. Merge from https://commits.webkit.org/251810@main * PerformanceTests/MotionMark/tests/master/resources/multiply.js: Increases complexity.
diff --git a/MotionMark/tests/master/resources/multiply.js b/MotionMark/tests/master/resources/multiply.js
@@ -37,7 +37,7 @@ var MultiplyStage = Utilities.createSubclass(Stage,
         ["opacity", 0, 1],
         ["display", "none", "block"]
     ],
-    totalRows: 45,
+    totalRows: 55,
 
     initialize: function(benchmark, options)
     {

Original file line number	Diff line number	Diff line change
`@@ -37,7 +37,7 @@ var MultiplyStage = Utilities.createSubclass(Stage,`
`37`	`37`	`["opacity", 0, 1],`
`38`	`38`	`["display", "none", "block"]`
`39`	`39`	`],`
`40`		`- totalRows: 45,`
	`40`	`+ totalRows: 55,`
`41`	`41`
`42`	`42`	`initialize: function(benchmark, options)`
`43`	`43`	`{`