Status

enhancement
a year ago
a year ago

People

(Reporter: cpeterson, Unassigned)

Tracking

Version 3
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [stylo:p3])

Reporter

Description

a year ago
@ Joel: can you please consider this bug for the PI backlog? It is not a high priority.

Now that StyleBench is running smoothly on Talos (bug 1422010), it would be good to also run it on AWFY so we can track changes in other browsers' performance.

Since we are already running StyleBench on Talos to catch regressions, we would not need to run StyleBench on AWFY frequently. Perhaps running StyleBench once a day with Firefox, Chrome, and WebKit nightly builds?
Flags: needinfo?(jmaher)
we can look into this- but it is lower in priority behind motionmark- right now our resources are focused on Mobile and doing the bare minimum on AWFY until later in the quarter or Q2.  I agree getting a regular update on comparisons to chrome/webkit would be good.
Component: Talos → AWFY
Flags: needinfo?(jmaher)
Reporter

Comment 2

a year ago
(In reply to Joel Maher ( :jmaher) (UTC-5) from comment #1)
> we can look into this- but it is lower in priority behind motionmark- right
> now our resources are focused on Mobile and doing the bare minimum on AWFY
> until later in the quarter or Q2.

Thanks! Yeah, running StyleBench on AWFY is definitely a lower priority than those other projects.
You need to log in before you can comment on or make changes to this bug.