Repository navigation
pystats: More traces created than optimizations attempted #116760
Description
Bug report
Bug description:
In the pystats for many benchmarks, such as hexiom, the number of traces created exceeds the number of optimization attempts. This doesn't make sense because a trace shouldn't ever be created unless we tried to create one first. Probably there is a case where the trace creation code is getting called where the trace attempt stat isn't incremented.
For example:
| Count | Ratio |
|---|---|
| Optimization attemptsⓘ | 1,540 |
| Traces createdⓘ | 52,900 |
| Trace stack overflowⓘ | 0 |
| Trace stack underflowⓘ | 16,060 |
| Trace too longⓘ | 0 |
| Trace too shortⓘ | 1,197,960 |
| Inner loop foundⓘ | 500 |
| Recursive callⓘ | 0 |
| Low confidenceⓘ | 100 |
| Executors invalidatedⓘ | 0 |
| Traces executedⓘ | 109,768,500 |
| Uops executedⓘ | 2,948,922,980 |
CPython versions tested on:
CPython main branch
Operating systems tested on:
Linux
Activity
pythongh-116760: Fix pystats for trace attempts
gh-116760: Fix pystats for trace attempts (GH-116761)
pythongh-116760: Fix pystats for trace attempts (pythonGH-116761)
pythongh-116760: Fix pystats for trace attempts (pythonGH-116761)
pythongh-116760: Fix pystats for trace attempts (pythonGH-116761)