Skip to content

Tell the compressor which serialized IDs the writer may emit - #9770

Open
mhk197 wants to merge 1 commit into
developfrom
mk/compressor-serialized-ids
Open

Tell the compressor which serialized IDs the writer may emit#9770
mhk197 wants to merge 1 commit into
developfrom
mk/compressor-serialized-ids

Tell the compressor which serialized IDs the writer may emit

85990c2
Select commit
Loading
Failed to load commit list.
CodSpeed HQ / CodSpeed Performance Analysis failed Sep 4, 2026 in 0s

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.

Open the report in CodSpeed to investigate

⚡ 6 improved benchmarks
❌ 2 regressed benchmarks
✅ 2191 untouched benchmarks
⏩ 206 skipped benchmarks1

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

Mode Benchmark BASE HEAD Efficiency
Simulation random_i8[0.8] 69.8 µs 99.3 µs -29.72%
WallTime mul_i32_nonnull_avx512 7 µs 7.8 µs -10.34%
WallTime arrow_checked_add_u32_neon[16384] 20.5 µs 12.7 µs +60.72%
Simulation random_i8[0.5] 91.3 µs 67.4 µs +35.4%
WallTime arrow_checked_add_u32_avx2[16384] 21.3 µs 17.7 µs +20.56%
Simulation allocate_drop_arrow[0] 456.9 ns 402.7 ns +13.45%
WallTime filtered_sink_i64_neon[NineNullsInTen] 28.4 µs 25.3 µs +12.14%
WallTime filtered_owned_i64_neon[NineNullsInTen] 28.4 µs 25.7 µs +10.63%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.


Comparing mk/compressor-serialized-ids (85990c2) with develop (0d9d5b8)

Open in CodSpeed

Footnotes

  1. 206 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.