Skip to content

Opt-in direct I/O reads, and what segment alignment is actually worth - #9838

Closed
joseph-isaacs wants to merge 5 commits into
developfrom
claude/direct-io-reads-perf-3b5kk2
Closed

joseph-isaacs wants to merge 5 commits into
developfrom
claude/direct-io-reads-perf-3b5kk2

fix(file): only group segments smaller than a block

95c4954
Select commit
Loading
Failed to load commit list.
CodSpeed / CodSpeed Performance Analysis failed Sep 14, 2026 in 0s

Performance Regression: -13.68%

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

⚡ 1 improved benchmark
❌ 4 regressed benchmarks
✅ 2234 untouched benchmarks
⏩ 176 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 arrow_checked_add_u32_neon[16384] 12.4 µs 20.4 µs -39.16%
❌ Simulation random_i16[0.95] 79.4 µs 97.4 µs -18.45%
❌ Simulation decompress[u64, (4000, 1024)] 71.4 µs 86.8 µs -17.7%
❌ WallTime words_gather_scalar_avx2[65536] 8.2 µs 9.4 µs -11.86%
⚡ Simulation random_i8[0.5] 93.7 µs 70.4 µs +33.18%

Tip

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


Comparing claude/direct-io-reads-perf-3b5kk2 (95c4954) with develop (d82de0e)

Open in CodSpeed

Footnotes

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