Sounds sensible - thanks Xidorn!
On Fri, Mar 31, 2017 at 5:44 PM, Xidorn Quan wrote:
> With bug 1350810 [1], Gecko's CI now uploads its generated binding files
> as an artifact for stylo builds. It is listed as
> "target.stylo-bindings.zip" in Job Details of stylo build tasks
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
wrote:
> On 2017-03-31 4:38 PM, Jack Moffitt wrote:
>
>> Together, these metrics will give us information on the graphical
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
Oh, and as for how I expect they'll be implemented:
Time to interaction sounds straightforward to me - on a
per-script-thread basis, track the start of the last 10s window that did
not contain a task that took longer than 50ms to execute. Whenever at
least 10s has gone by since the start of
Back in September, Till shared an update [1] from dev-platform about the
Progressive Web Metrics that the Blink team is championing. I've been
looking into how that effort is going in Firefox and Blink, and whether
we should be adopting some of them.
Overview:
We should implement the Time to
This is a great write-up on the details of our compilation process, thanks
Simon!
> There is a risk that preserved files could be left by a previous builds
in a broken state, leading to failures that only happen on CI. We’re
monitoring this and will consider reverting this change it this turns
If you build Servo a lot you may have noticed that compilation times
have improved over the last few months. This is combination of multiple
factors.
# Compiler optimization
Plain old optimization of the compiler’s code. Sometimes a rustup makes
things a bit faster without us changing
7 matches
Mail list logo