fix: omit baseline-only formats from the file-size report - #9589
fix: omit baseline-only formats from the file-size report#9589joseph-isaacs wants to merge 1 commit into
Conversation
A benchmark run that skips a format (for example vortex-compact) produced no file-size rows for it, so the PR comment rendered every baseline file of that format as shrinking to 0 B (-100.0%). Scope the baseline rows to the (benchmark, scale factor, format) combinations the PR run actually produced, so skipped formats are omitted instead of reported as deleted. Signed-off-by: Joe Isaacs <joe.isaacs@live.co.uk>
Merging this PR will degrade performance by 11.38%
|
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | Simulation | cold_misaligned[(16, 64)] |
380.2 µs | 429.1 µs | -11.38% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing ji/eager-knuth-yrk9n9 (c2ac7c3) with develop (e4b3421)
Footnotes
-
54 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. ↩
Polar Signals Profiling ResultsLatest Run
Powered by Polar Signals Cloud |
Benchmarks: PolarSignals Profiling 📖Commits: PR datafusion / vortex-file-compressed / ns (1.002x ➖, 1↑ 1↓)
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.994x ➖, 0↑ 0↓)
datafusion / parquet / ns (1.021x ➖, 0↑ 2↓)
duckdb / vortex-file-compressed / ns (0.982x ➖, 0↑ 0↓)
duckdb / parquet / ns (1.000x ➖, 0↑ 0↓)
No file size changes detected. |
Benchmarks: FineWeb NVMe 📖Commits: PR How to read Verdict and Engines
datafusion / vortex-file-compressed / ns (1.036x ➖, 0↑ 3↓)
datafusion / parquet / ns (1.006x ➖, 0↑ 0↓)
duckdb / vortex-file-compressed / ns (0.963x ➖, 1↑ 1↓)
duckdb / parquet / ns (1.004x ➖, 0↑ 0↓)
No file size changes detected. |
Benchmarks: Clickbench Sorted on NVME 📖Commits: PR How to read Verdict and Engines
datafusion / vortex-file-compressed / ns (0.974x ➖, 2↑ 0↓)
datafusion / parquet / ns (1.000x ➖, 0↑ 0↓)
duckdb / vortex-file-compressed / ns (1.020x ➖, 0↑ 1↓)
duckdb / parquet / ns (1.018x ➖, 0↑ 0↓)
File Size Changes (100 files changed, -0.0% overall, 55↑ 45↓)
Totals:
|
Benchmarks: TPC-DS SF=1 on NVME 📖Commits: PR How to read Verdict and Engines
datafusion / vortex-file-compressed / ns (1.002x ➖, 0↑ 0↓)
datafusion / parquet / ns (1.007x ➖, 0↑ 1↓)
duckdb / vortex-file-compressed / ns (1.005x ➖, 1↑ 5↓)
duckdb / parquet / ns (1.012x ➖, 2↑ 9↓)
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.997x ➖, 0↑ 0↓)
datafusion / parquet / ns (0.996x ➖, 0↑ 0↓)
duckdb / vortex-file-compressed / ns (1.011x ➖, 0↑ 0↓)
duckdb / parquet / ns (1.003x ➖, 1↑ 1↓)
No file size changes detected. |
Benchmarks: FineWeb S3 📖Commits: PR How to read Verdict and Engines
datafusion / vortex-file-compressed / ns (0.862x ➖, 1↑ 0↓)
datafusion / parquet / ns (0.955x ➖, 0↑ 0↓)
duckdb / vortex-file-compressed / ns (0.983x ➖, 0↑ 0↓)
duckdb / parquet / ns (1.001x ➖, 3↑ 3↓)
|
Benchmarks: Statistical and Population Genetics 📖Commits: PR How to read Verdict and Engines
duckdb / vortex-file-compressed / ns (1.032x ➖, 0↑ 2↓)
duckdb / parquet / ns (1.000x ➖, 0↑ 0↓)
No file size changes detected. |
Benchmarks: Clickbench on NVME 📖Commits: PR How to read Verdict and Engines
datafusion / vortex-file-compressed / ns (0.999x ➖, 0↑ 0↓)
datafusion / parquet / ns (0.998x ➖, 0↑ 0↓)
duckdb / vortex-file-compressed / ns (1.000x ➖, 1↑ 0↓)
duckdb / parquet / ns (1.001x ➖, 0↑ 1↓)
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 (0.967x ➖, 1↑ 0↓)
datafusion / parquet / ns (0.970x ➖, 0↑ 0↓)
duckdb / vortex-file-compressed / ns (1.008x ➖, 1↑ 0↓)
duckdb / parquet / ns (1.023x ➖, 0↑ 0↓)
|
Summary
Benchmark PR comments rendered every baseline file of a format the PR run skipped as shrinking to 0 B (-100.0%). For example, on #9544 the SQL benchmark comments listed all
vortex-compactfiles asX MB → 0 B (-100.0%)because that run did not include the vortex-compact preset, so the comparison mistook "not run" for "deleted".Changes
format_file_size_reportinscripts/compare-benchmark-jsons.pyscoped the baseline rows only to(benchmark, scale_factor)pairs present in the PR run, so a format missing from the PR run fell through topr_data.get(key, 0)and reported as 0 B. The scope filter now includes the format, so baseline rows for a format the PR run skipped entirely are omitted from the report. A file genuinely missing within a format that did run still reports as going to zero.Tested with a new case in
scripts/tests/test_benchmark_reporting.py(test_file_size_report_omits_formats_the_pr_run_skipped); all 25 tests in the module pass.Generated by Claude Code