Skip to content

Don't pass extension arrays through the compressor unchanged - #10424

Merged
robert3005 merged 2 commits into
developfrom
rk/compress-explicit-fallback
Oct 19, 2026
Merged

robert3005 merged 2 commits into
developfrom
rk/compress-explicit-fallback

Conversation

@robert3005

@robert3005 robert3005 commented Oct 10, 2026 •

Copy link
Copy Markdown
Contributor

The compressor indicates whether the array was returned unchanged. Extension scheme canonicalises input and only keeps extension scheme compressed arrays if they actually compressed anything instead of returning input unchanged

fix #10417

@codspeed

codspeed Bot commented Oct 10, 2026 •

Copy link
Copy Markdown

Merging this PR will degrade performance by 23.35%

⚠️ 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.

⚠️ 1 benchmark measured no execution time

Nothing ran under measurement, usually because the compiler removed the code under test. This result is not comparable, so it counts as unchanged.

Preventing compiler optimizations

⚠️ 16 benchmarks spent significant time in system calls

System calls cannot be consistently instrumented, so they are not included in the measure, which understates the real cost. Please switch to the Walltime instrument to accurately measure system calls.

Measurement and system calls

ℹ️ 40 benchmarks have no flame graph

The flamegraph could not be generated because we failed to resolve the symbols in the profiling trace. This happens when we fail to harvest information about language frames.

⚠️ 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

❌ 8 regressed benchmarks
✅ 2400 untouched benchmarks
⏩ 12 skipped benchmarks1

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

Mode Benchmark BASE HEAD Efficiency
❌ WallTime filter_neon[8] 959 ns 1,583 ns -39.42%
❌ WallTime filter_neon[64] 1.8 µs 2.6 µs -30.02%
❌ WallTime threshold_neon[8] 1.4 µs 1.9 µs -26.53%
❌ WallTime threshold_neon[80] 3.5 µs 4.6 µs -23.2%
❌ WallTime threshold_neon[64] 2.7 µs 3.5 µs -23.18%
❌ WallTime filter_neon[80] 2.7 µs 3.2 µs -17.6%
❌ Simulation isolated_runs[u32, (16, 0)] 78.5 µs 88.6 µs -11.44%
❌ ℹ️ Simulation test_scan_filter[int] 3.1 ms 3.5 ms -11.18%

Tip

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


Comparing rk/compress-explicit-fallback (8d11832) with develop (8c2534e)

Open in CodSpeed

Footnotes

  1. 12 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. ↩

@asubiotto

Copy link
Copy Markdown
Contributor

We're currently blocked on upgrading vortex because of #10417

When no scheme compresses a canonical extension array, `choose_and_compress`
returns the input itself, and the extension branch kept it whenever its
`nbytes` beat the compressed storage. Canonicalizing an extension array only
canonicalizes the top level of its storage, so the input can still hold lazy
arrays such as `vortex.slice`, which cannot be serialized. A UUID column
mixing a dense chunk with a slice of a sparse one hit this on write
(#10417).

Use the compressed storage whenever no scheme produced a new array.

Signed-off-by: Claude <noreply@anthropic.com>

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015XzXtnsrnEsBNVa9R2VqKQ
`choose_and_compress` returned its input whenever no scheme beat it, so every
caller got an `ArrayRef` that may or may not have been compressed. That is a
valid result for leaf arrays, but not for extension arrays, whose canonical
form leaves the storage below its top level lazy; the extension branch had to
detect the passthrough by pointer identity.

Return a `Selection` that says whether anything was compressed, so each caller
picks its fallback explicitly and the extension branch falls back to its
compressed storage by construction.

Signed-off-by: Claude <noreply@anthropic.com>

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015XzXtnsrnEsBNVa9R2VqKQ
@robert3005
robert3005 force-pushed the rk/compress-explicit-fallback branch from c3ad942 to 8d11832 Compare October 19, 2026 18:08
@robert3005
robert3005 enabled auto-merge (squash) October 19, 2026 18:08
@robert3005
robert3005 merged commit 5d8fa18 into develop Oct 19, 2026
85 of 86 checks passed
@robert3005
robert3005 deleted the rk/compress-explicit-fallback branch October 19, 2026 18:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog/fix A bug fix

Projects

None yet

3 participants