Skip to content

perf(bench): generate TPC-H Parquet in parallel parts on a shared work queue - #10557

Draft
joseph-isaacs wants to merge 1 commit into
developfrom
ji/parallel-datagen
Draft

joseph-isaacs wants to merge 1 commit into
developfrom
ji/parallel-datagen

perf(bench): generate TPC-H Parquet in parallel parts on a shared wor…

4e79254
Select commit
Loading
Failed to load commit list.
CodSpeed / CodSpeed Performance Analysis failed Oct 16, 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.

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

⚡ 3 improved benchmarks
❌ 1 regressed benchmark
✅ 2243 untouched benchmarks
⏩ 12 skipped benchmarks1

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

Mode Benchmark BASE HEAD Efficiency
❌ WallTime deferred_i64_avx2[PerRowPerRow] 10.1 µs 11.6 µs -13.28%
⚡ Simulation take_map[(0.1, 1.0)] 352.2 µs 221.2 µs +59.22%
⚡ Simulation take_map[(0.1, 0.5)] 182.6 µs 146.4 µs +24.72%
⚡ Simulation take_map[(0.1, 0.05)] 87 µs 77.4 µs +12.42%

Tip

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


Comparing ji/parallel-datagen (4e79254) with develop (6eae823)

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