Closed Bug 1601667 Opened 4 years ago Closed 4 years ago

Measure raptor performance on Pixel 2 in CI with WebRender

Categories

(Core :: Graphics: WebRender, task, P3)

task

Tracking

()

RESOLVED INVALID

People

(Reporter: aosmond, Assigned: aosmond)

References

Details

Currently the raptor tests run on the Pixel 2 on treeherder, but we force disable WebRender anywhere that doesn't specifically opt into it on CI, so it tests non-WebRender performance. We don't want to switch the perf tests to just use WR, because the Pixel 2 is the only device we have in CI for measuring performance (and so is a useful proxy in general for Android performance), but it would be useful to compare the WR and non-WR results against each other and possibly create a new job that only runs on request.

Blocks: wr-73-android
No longer blocks: wr-android

The results are noisy as always, but I think the key take away here is that our cold startup has likely "regressed" by quite a bit:

https://wiki.mozilla.org/TestEngineering/Performance/Raptor#Cold_Page-Load

It appears the Android app data is deleted, so I guess any cached compiled shaders need to be rebuilt. I don't think any other results are very notable at this time. There are no motionmark benchmarks able to be run on Android in CI, so we can't really see WR's strengths present in the available test suite.

Hey Andrew, what is the status of this task?

Flags: needinfo?(aosmond)

I ran all the tests that I could.

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