Open Bug 1876095 Opened 10 months ago Updated 10 months ago

Document our thresholds

Categories

(Core :: JavaScript Engine: JIT, task, P3)

Product:
Core
Component:
JavaScript Engine: JIT
Type:
task

Tracking

()

People

(Reporter: yulia, Unassigned)

References

(Blocks 1 open bug)

Details

Every now and then, someone will ask "are our JIT thresholds right?". They will then go through the arduous process of testing our thresholds, either programmatically or through sampling, to come (usually) to the conclusion of "probably".

I've just gone through the process myself of exhaustively searching our jit thresholds. I've got the script, and a jupyter notebook that spits out pretty results. We can use this as the basis for a CI task, that will generate an HTML artifact and alert us when too many tests do not benefit from a given benchmark.

This way we will know how our thresholds have been validated, and we will be alerted if things shift too much.

You need to log in before you can comment on or make changes to this bug.