Upgrade pyO3 to 0.29.0#8462
Conversation
Signed-off-by: Robert Kruszewski <github@robertk.io>
AdamGS
left a comment
There was a problem hiding this comment.
If CI is happy, I'm happy
Merging this PR will not alter performance
|
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | WallTime | cuda/bitpacked_u8/unpack/3bw[100M] |
299 µs | 350.8 µs | -14.77% |
| ❌ | Simulation | bitwise_not_vortex_buffer_mut[128] |
186.1 ns | 215.3 ns | -13.55% |
| ❌ | Simulation | bitwise_not_vortex_buffer_mut[1024] |
246.4 ns | 275.6 ns | -10.58% |
| ⚡ | Simulation | take_map[(0.1, 0.5)] |
1,180.4 µs | 992.3 µs | +18.95% |
| ⚡ | Simulation | take_map[(0.1, 1.0)] |
1.9 ms | 1.7 ms | +13.78% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing rk/pyo3 (c885434) with develop (4b867a0)
Footnotes
-
10 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. ↩
This lets us get over the security advisory