On 2017-04-12 5:33 AM, Jan de Mooij wrote: > On Tue, Apr 11, 2017 at 11:25 PM, Steve Fink <sf...@mozilla.com> wrote: > >> The juxtaposition of telemetry and the IC logger makes me wonder -- is it, >> or could it be, lightweight enough to report on via telemetry? It would be >> pretty cool to be able to drive work off of what the bulk of our users >> could make use of. > > > We could for example record - for each IC kind - how often we managed to > attach a stub (this should approach 100%) or how many ICs were marked as > 'Generic' (= we gave up on optimizing for some reason). It's not very clear > how actionable this data would be (the IC logger stores additional > information about the IC inputs) but it might reveal something interesting > or catch regressions. There are also other JIT things we could add > telemetry for, for instance IonBuilder abort reasons. It's definitely > something to think about.
Is any of this something that can be exposed in the profiler UI somehow so that people like me who sometimes file bugs providing a profile of something being slow on a website can provide an IC log or some such? _______________________________________________ dev-tech-js-engine-internals mailing list dev-tech-js-engine-internals@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
