fix: remove vulnerable thrift dependency - #26
2 benchmarks regressed
⚠️ Unknown Walltime execution environment detected
Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.
For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.
⚠️ Different runtime environments detected
Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.
⚡ 2 improved benchmarks
❌ 2 regressed benchmarks
✅ 28 untouched benchmarks
⏩ 2 skipped benchmarks1
Warning
Please fix the performance issues or acknowledge them on CodSpeed.
Performance Changes
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | WallTime | decompress_all[("p_name", 16)] |
907.4 µs | 1,022.9 µs | -11.29% |
| ❌ | WallTime | decompress_all[("p_name", 12)] |
1.1 ms | 1.3 ms | -10.99% |
| ⚡ | WallTime | decompress_all[16] |
764.9 µs | 659.5 µs | +15.98% |
| ⚡ | WallTime | decompress_all[12] |
750.5 µs | 663.2 µs | +13.15% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing fix/update-parquet-dependencies (0f7824c) with develop (18e5f61)
Footnotes
-
2 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. ↩