Document the bytecode compilation timeout override#20186
Conversation
2fd43e2 to
b1c42c8
Compare
cf63fb2 to
7583835
Compare
Merging this PR will degrade performance by 22.87%
|
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | Simulation | resolve_warm_airflow |
490.4 ms | 880.5 ms | -44.3% |
| ❌ | Simulation | resolve_warm_jupyter |
48.3 ms | 83.9 ms | -42.45% |
| ❌ | Simulation | resolve_warm_jupyter_universal |
157.5 ms | 217.9 ms | -27.73% |
| ⚡ | Simulation | unzip_wheel_many_files |
87.5 ms | 79.3 ms | +10.3% |
| ⚡ | Simulation | prepare_wheel_many_files |
108.7 ms | 101.7 ms | +6.82% |
Tip
Investigate this regression with the CodSpeed MCP and your agent.
Comparing zaniebot:zb/bytecode-timeout-doc (2fd43e2) with main (bc286d3)2
Footnotes
-
18 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩
-
No successful run was found on
zb/pip-install-compile-bytecode(ac8a461) during the generation of this report, somain(bc286d3) was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩
2ea23ce
into
astral-sh:zb/pip-install-compile-bytecode
Document the existing `UV_COMPILE_BYTECODE_TIMEOUT` override alongside the compilation helper, including that a value of `0` disables the timeout. This replaces #20186, which was merged into its temporary stacked base after #19914 had already landed rather than into `main`. Co-authored-by: Zanie Blue <contact@zanie.dev>
Document the bytecode compilation timeout override alongside the compilation helper. This makes the default 60-second limit and the
UV_COMPILE_BYTECODE_TIMEOUToverride discoverable, including that setting it to0disables the timeout.