On Friday, March 31, 2017 at 4:38:25 PM UTC-4, Jack Moffitt wrote: > > Together, these metrics will give us information on the graphical timeline > > showing: > > * how long after a page was requested before the first visual change > > occurred > > * how long after that before the first nontrivial visual content appeared > > * how long after the page was requested before it was in a state that could > > respond to user input with low latency > > Will we be able to get this information during CI-style automated > runs? I would like to start recording these and watching for > regressions. I don't much care if they are accessed via JS APIs or > through some other mechanism, just that they are exposed some way we > can get at them in automation. > > jack.
This sounds like a good candidate to include in Talos and other tools that measure pageload related performance. thinking more, having this in our frameworks (like web-platform-tests, mochitest, reftest) would be nice to keep reference to, it might be more complicated to store that data long term, but maybe setting a baseline and failing a test if it crosses a 2x threshold _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
