Skip to content

fix: omit zone-map stats that a nullable struct's nulls would corrupt - #10413

Merged
robert3005 merged 5 commits into
developfrom
ji/magical-bell-b84xbc
Oct 12, 2026
Merged

robert3005 merged 5 commits into
developfrom
ji/magical-bell-b84xbc

chore: note how zone maps under nullable structs can come back

d00d4e2
Select commit
Loading
Failed to load commit list.
CodSpeed / CodSpeed Performance Analysis failed Oct 12, 2026

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.

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

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

⚡ 5 improved benchmarks
❌ 1 regressed benchmark
✅ 2201 untouched benchmarks

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

Mode Benchmark BASE HEAD Efficiency
❌ WallTime bitpack_blocked_compress_avx512 4.9 µs 5.7 µs -13.94%
⚡ WallTime threshold_neon[8] 4 µs 3 µs +33.84%
⚡ WallTime filter_neon[64] 3.5 µs 2.9 µs +19.76%
⚡ WallTime threshold_neon[80] 5.8 µs 4.8 µs +19.15%
⚡ WallTime threshold_neon[64] 5.3 µs 4.5 µs +18.52%
⚡ WallTime filter_neon[80] 3.5 µs 3.2 µs +11.25%

Tip

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


Comparing ji/magical-bell-b84xbc (d00d4e2) with develop (9d5a844)

Open in CodSpeed