Simplify benchmark comments - #8581
Conversation
Signed-off-by: Adam Gutglick <adam@spiraldb.com>
Polar Signals Profiling ResultsLatest Run
Powered by Polar Signals Cloud |
Benchmarks: PolarSignals ProfilingVortex (geomean): 0.991x ➖ How to read Verdict and Engines
datafusion / vortex-file-compressed (0.991x ➖, 1↑ 1↓)
No file size changes detected. |
Benchmarks: TPC-H SF=1 on NVMEVerdict: No clear signal (low confidence) How to read Verdict and Engines
datafusion / vortex-file-compressed (0.982x ➖, 0↑ 0↓)
datafusion / vortex-compact (0.980x ➖, 0↑ 0↓)
datafusion / parquet (0.978x ➖, 1↑ 0↓)
datafusion / arrow (0.962x ➖, 2↑ 1↓)
duckdb / vortex-file-compressed (0.975x ➖, 0↑ 0↓)
duckdb / vortex-compact (0.976x ➖, 0↑ 0↓)
duckdb / parquet (0.985x ➖, 0↑ 0↓)
duckdb / duckdb (0.977x ➖, 0↑ 0↓)
File Size Changes (10 files changed, -0.0% overall, 6↑ 4↓)
Totals:
|
Benchmarks: FineWeb NVMeVerdict: No clear signal (low confidence) How to read Verdict and Engines
datafusion / vortex-file-compressed (0.908x ➖, 4↑ 0↓)
datafusion / vortex-compact (0.933x ➖, 1↑ 0↓)
datafusion / parquet (0.922x ➖, 3↑ 0↓)
duckdb / vortex-file-compressed (0.983x ➖, 1↑ 1↓)
duckdb / vortex-compact (0.936x ➖, 1↑ 0↓)
duckdb / parquet (0.942x ➖, 0↑ 0↓)
File Size Changes (1 files changed, -0.0% overall, 0↑ 1↓)
Totals:
|
Benchmarks: TPC-DS SF=1 on NVMEVerdict: No clear signal (low confidence) How to read Verdict and Engines
datafusion / vortex-file-compressed (1.022x ➖, 0↑ 2↓)
datafusion / vortex-compact (1.030x ➖, 0↑ 6↓)
datafusion / parquet (1.011x ➖, 2↑ 3↓)
duckdb / vortex-file-compressed (1.025x ➖, 2↑ 9↓)
duckdb / vortex-compact (1.029x ➖, 1↑ 3↓)
duckdb / parquet (1.016x ➖, 1↑ 1↓)
duckdb / duckdb (1.024x ➖, 1↑ 4↓)
File Size Changes (5 files changed, +0.0% overall, 4↑ 1↓)
Totals:
|
Merging this PR will improve performance by 11.9%
|
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ⚡ | Simulation | encode_varbin[(1000, 4)] |
157 µs | 139.8 µs | +12.34% |
| ⚡ | Simulation | encode_varbin[(1000, 32)] |
162.5 µs | 144.8 µs | +12.22% |
| ⚡ | Simulation | encode_varbin[(1000, 8)] |
157.3 µs | 140.4 µs | +12.05% |
| ⚡ | Simulation | encode_varbin[(1000, 2)] |
156.1 µs | 140.7 µs | +10.98% |
Tip
Curious why this is faster? Comment @codspeedbot explain why this is faster on this PR, or directly use the CodSpeed MCP with your agent.
Comparing adamg/simplify-sql-benchmarks-comments (9fedbc1) with develop (e2478aa)
Footnotes
-
4 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. ↩
Benchmarks: Statistical and Population GeneticsVerdict: No clear signal (low confidence) How to read Verdict and Engines
duckdb / vortex-file-compressed (0.979x ➖, 0↑ 0↓)
duckdb / vortex-compact (0.992x ➖, 0↑ 0↓)
duckdb / parquet (0.983x ➖, 0↑ 0↓)
File Size Changes (1 files changed, -0.0% overall, 0↑ 1↓)
Totals:
|
🚨🚨🚨❌❌❌ SQL BENCHMARK FAILED ❌❌❌🚨🚨🚨Benchmark |
Benchmarks: FineWeb S3Verdict: No clear signal (environment too noisy confidence) How to read Verdict and Engines
datafusion / vortex-file-compressed (1.352x ❌, 0↑ 4↓)
datafusion / vortex-compact (1.248x ➖, 0↑ 2↓)
datafusion / parquet (1.081x ➖, 0↑ 2↓)
duckdb / vortex-file-compressed (1.085x ➖, 0↑ 1↓)
duckdb / vortex-compact (1.257x ➖, 0↑ 4↓)
duckdb / parquet (1.078x ➖, 0↑ 0↓)
|
Rational for this change
#8465 made the SQL benchmarks comments and titles unnecessarily verbose, I was too excited to merge it to just get a quicker feedback loop.
What changes are included in this PR?
Restores how SQL benchmarks comments are displayed - one per benchmark, regardless of what workflow ran it.
What APIs are changed? Are there any user-facing changes?
N/A