Split SQL PR benchmarks into bench-sql and bench-sql-extended - #10213
Conversation
Polar Signals Profiling ResultsLatest Run
Powered by Polar Signals Cloud |
Benchmarks: PolarSignals Profiling 📖Commits: PR datafusion / vortex-file-compressed / ns (0.998x ➖, 0↑ 0↓)
No file size changes detected. |
Benchmarks: FineWeb NVMe 📖Commits: PR How to read Verdict and Engines
datafusion / vortex-file-compressed / ns (1.001x ➖, 0↑ 0↓)
datafusion / parquet / ns (1.004x ➖, 0↑ 0↓)
duckdb / vortex-file-compressed / ns (1.014x ➖, 3↑ 3↓)
duckdb / parquet / ns (1.002x ➖, 0↑ 0↓)
No file size changes detected. |
Benchmarks: TPC-H SF=1 on NVME 📖Commits: PR How to read Verdict and Engines
datafusion / vortex-file-compressed / ns (0.999x ➖, 0↑ 0↓)
datafusion / parquet / ns (0.999x ➖, 0↑ 0↓)
duckdb / vortex-file-compressed / ns (0.997x ➖, 0↑ 0↓)
duckdb / parquet / ns (0.993x ➖, 0↑ 0↓)
No file size changes detected. |
Benchmarks: Clickbench on NVME 📖Commits: PR How to read Verdict and Engines
datafusion / vortex-file-compressed / ns (1.003x ➖, 0↑ 0↓)
datafusion / parquet / ns (1.005x ➖, 0↑ 0↓)
duckdb / vortex-file-compressed / ns (1.026x ➖, 0↑ 3↓)
duckdb / parquet / ns (1.004x ➖, 1↑ 1↓)
No file size changes detected. |
Benchmarks: TPC-DS SF=1 on NVME 📖Commits: PR How to read Verdict and Engines
datafusion / vortex-file-compressed / ns (1.002x ➖, 0↑ 1↓)
datafusion / parquet / ns (1.005x ➖, 0↑ 0↓)
duckdb / vortex-file-compressed / ns (1.004x ➖, 1↑ 2↓)
duckdb / parquet / ns (0.997x ➖, 3↑ 3↓)
No file size changes detected. |
Benchmarks: TPC-H SF=10 on NVME 📖Commits: PR How to read Verdict and Engines
datafusion / vortex-file-compressed / ns (0.999x ➖, 0↑ 0↓)
datafusion / parquet / ns (0.997x ➖, 0↑ 0↓)
duckdb / vortex-file-compressed / ns (0.983x ➖, 1↑ 0↓)
duckdb / parquet / ns (0.986x ➖, 1↑ 0↓)
No file size changes detected. |
Benchmarks: TPC-H SF=1 on S3 📖Commits: PR How to read Verdict and Engines
datafusion / vortex-file-compressed / ns (1.045x ➖, 0↑ 1↓)
datafusion / parquet / ns (0.931x ➖, 1↑ 0↓)
duckdb / vortex-file-compressed / ns (0.971x ➖, 0↑ 1↓)
duckdb / parquet / ns (0.887x ➖, 1↑ 0↓)
|
Keep seven core SQL benchmark jobs under action/bench-sql and dispatch all regular benchmarks through action/bench-sql-extended. Preserve current develop coverage, including DataFusion statpopgen targets, and update matrix coverage tests and documentation. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Joe Isaacs <joe.isaacs@live.co.uk>
9d5c97c to
f5417fb
Compare
Merging this PR will improve performance by 85.6%
|
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ⚡ | Simulation | all_valid_exclusive[65536] |
6.9 ms | 3.5 ms | +95.37% |
| ⚡ | Simulation | all_valid_exclusive[4096] |
438.3 µs | 231.1 µs | +89.61% |
| ⚡ | Simulation | nullable_exclusive[4096] |
350.5 µs | 193.2 µs | +81.4% |
| ⚡ | Simulation | nullable_exclusive[65536] |
4.9 ms | 2.8 ms | +76.56% |
| 🆕 | Simulation | outlined_nullable_exclusive[4096] |
N/A | 368.6 µs | N/A |
| 🆕 | Simulation | outlined_nullable_exclusive[65536] |
N/A | 5.2 ms | N/A |
Tip
Curious why performance improved? Comment @codspeedbot explain why performance improved on this PR, or directly use the CodSpeed MCP with your agent.
Comparing ji/bench-sql-extended (f5417fb) with develop (48162f0)2
Footnotes
-
503 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. ↩
-
No successful run was found on
develop(8b7a257) during the generation of this report, so 48162f0 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩
action/bench-sqlcurrently runs ten SQL benchmark jobs. This change reduces it to seven core jobs and addsaction/bench-sql-extendedfor all thirteen regular SQL benchmarks.prpreset retains Clickbench, TPC-H SF1 on NVMe and S3, TPC-H SF10 on NVMe, TPC-DS, local FineWeb, and PolarSignals.pr-fullpreset, including the additional benchmarks and its Vortex Compact and DuckDB-format targets.develop.The repository's
action/bench-sql-extendedlabel is now configured.Validation: the previous revision passed CI and all seven core SQL benchmark jobs. After rebasing onto
develop, the statpopgen conflict and its affected test were updated. Local test and lint commands were not rerun, following the repository's opt-in verification guidance; fresh GitHub CI will validate the updated commit.