Skip to content

Remove the unstable encodings feature - #9710

Open
robert3005 wants to merge 5 commits into
developfrom
rk/remove-unstable-encodings
Open

Remove the unstable encodings feature#9710
robert3005 wants to merge 5 commits into
developfrom
rk/remove-unstable-encodings

more

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

1 benchmark 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

⚡ 4 improved benchmarks
❌ 1 regressed benchmark
✅ 2236 untouched benchmarks
⏩ 164 skipped benchmarks1
🗄️ 1 archived benchmark run2

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

Mode Benchmark BASE HEAD Efficiency
WallTime cuda/bitpacked_u8/unpack/3bw[100M] 300.4 µs 347.4 µs -13.54%
WallTime arrow_checked_add_u32_neon[16384] 20.5 µs 12.8 µs +60.52%
Simulation decompress[u64, (4000, 1024)] 85.5 µs 70.4 µs +21.59%
WallTime filtered_sink_i64_neon[NineNullsInTen] 28.4 µs 25.4 µs +11.83%
WallTime filtered_owned_i64_neon[NineNullsInTen] 28.4 µs 25.5 µs +11.48%

Tip

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


Comparing rk/remove-unstable-encodings (0af6657) with develop (0d9d5b8)3

Open in CodSpeed

Footnotes

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

  2. 1 benchmark was run, but is now archived. If it was deleted in another branch, consider rebasing to remove it from the report. Instead if it was added back, click here to restore it.

  3. No successful run was found on develop (a997c3f) during the generation of this report, so 0d9d5b8 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report.