JIT coverage can be improved considerably
Open
@Fidget-Spinner is already working on this.
Since Dec 29, 2025.
interpreter-core
topic-JIT
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
JIT coverage is still quite variable. For some benchmarks, e.g. richards it is close to 100%.
For others, much lower:
https://github.com/savannahostrowski/pyperf_bench/blob/main/profiling/jit.svg
Note: A fair bit of the time attributed to the interpreter is frame cleanup, so makes the interpreter fractions look larger than they are.
We can increase JIT coverage, by:
- Treating dynamic exits, like side exits: warming up and compiling a new side trace.
- Adding possible jit entry points at function entries, as well as backward edges.
Linked PRs
- gh-143391
- gh-143977
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.