On Tue, Apr 11, 2017 at 9:34 PM, Jason Orendorff
> - Bigger projects, like Waldo's work on parsing and djvj et al's work on GC
> scheduling, are undertaken when we have stuff that has been showing up on
> profiles "forever". This kind of work isn't driven by any one particular
> measurement, like a benchmark.
I think telemetry is useful to drive the GC work. We know how many of our
GCs are non-incremental (and for what reason). Same for full (all zone)
GCs. We know how long our GC slices are. There may be data that's not
captured by telemetry, but the data we do have seems pretty valuable anyway.
Generally, I think we're working on stuff that makes sense (and have been
> all along), but it's still not guaranteed to be representative of the web
> as users see it. Is that fair? What else should we be doing?
On the JIT/IC side, evilpie's IC logger/analyzer has been very useful. The
past months we've fixed tons of (often easy to fix) perf bugs that showed
up on actual websites our users visit.
> dev-tech-js-engine-internals mailing list