From:  Ehsan Akhgari <ehsan.akhgari@gmail.com>
Date:  12 Apr 2017 21:38:20 Hong Kong Time
Newsgroup:  news.mozilla.org/mozilla.dev.tech.js-engine.internals
Subject:  

Re: How JS team members decide what to work on

NNTP-Posting-Host:  63.245.214.181

On 2017-04-12 5:33 AM, Jan de Mooij wrote:
> On Tue, Apr 11, 2017 at 11:25 PM, Steve Fink  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?