Severe performance degradation for tracing under 3.11
Open
@markshannon is already working on this.
Since Jul 3, 2022.
3.11
interpreter-core
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
Bug report
Coverage.py is seeing a significant increase in overhead for tracing code in 3.11 compared to 3.10: https://github.com/nedbat/coveragepy/issues/1287
As an example:
| cov | proj | python3.10 | python3.11 | 3.11 vs 3.10 |
|---|---|---|---|---|
| none | bug1339.py | 0.184 s | 0.142 s | 76% |
| none | bm_sudoku.py | 10.789 s | 9.901 s | 91% |
| none | bm_spectral_norm.py | 14.305 s | 9.185 s | 64% |
| 6.4.1 | bug1339.py | 0.450 s | 0.854 s | 189% |
| 6.4.1 | bm_sudoku.py | 27.141 s | 55.504 s | 204% |
| 6.4.1 | bm_spectral_norm.py | 36.793 s | 67.970 s | 184% |
(This is the output of lab/benchmark.py.)
Your environment
- CPython versions tested on: 3.10, 3.11
- Operating system and architecture: MacOS, Intel
Linked PRs
- gh-108028
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.