Additionally, the existing profiling infrastructure can already dump its raw data as a TSV file.
On Fri, Mar 31, 2017 at 1:51 PM, Josh Matthews <j...@joshmatthews.net> wrote: > On 2017-03-31 4:38 PM, 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. >> >> > We could add a flag that prints meaningful messages to stdout for > top-level browsing contexts when these timestamps are recorded. Seems like > it shouldn't be a big deal. > > Cheers, > Josh > > _______________________________________________ > dev-servo mailing list > dev-servo@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-servo > _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
