Closed Bug 1603263 (fission-motionmark) Opened 5 years ago Closed 4 years ago

Verify Fission does not regress motionmark-htmlsuite or motionmark-animometer performance

Categories

(Core :: Graphics, task, P3)

Product:
Core
Component:
Graphics
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Project Flags:
Fission Milestone M7

People

(Reporter: cpeterson, Unassigned)

References

(Blocks 2 open bugs)

Details

(Whiteboard: fission-perf)

Before we enable Fission in Nightly (M6), we should manually verify that Fission doesn't regress motionmark-htmlsuite or motionmark-animometer performance on Windows, macOS, or Linux.

We don't expect Fission to impact MotionMark, so we don't want to waste the time and money to run MotionMark-Fis on mozilla-central and autoland.

https://browserbench.org/MotionMark1.1/about.html

Blocks: fission-perf
Alias: fission-motionmark
Blocks: motionmark

Enabling benchmarks in automation and verifying we have no perf regressions is a Fission Nightly blocker (milestone M6c).

Fission Milestone: M6 → M6c
Flags: needinfo?(rjesup)

No impact expected. Once we monitor in fission we can likely close it (or do some manual runs)

M7

Fission Milestone: M6c → M7
Whiteboard: fission-perf

Checked on arewefastyet for linux and windows (we're not running it on mac).

Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(rjesup)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.