Skip to content

Fix datafusion v2 statistics precision - #10835

Merged
gatesn merged 4 commits into
developfrom
ngates/datafusion-statistics-precision
Oct 26, 2026
Merged

gatesn merged 4 commits into
developfrom
ngates/datafusion-statistics-precision

Conversation

@gatesn

@gatesn gatesn commented Oct 26, 2026

Copy link
Copy Markdown
Contributor

The v2 VortexDataSource reports incorrect statistics when there are filter expressions or limits.

Signed-off-by: Nicholas Gates <nick@nickgates.com>
Signed-off-by: Nicholas Gates <nick@nickgates.com>
Signed-off-by: Nicholas Gates <nick@nickgates.com>
Signed-off-by: Nicholas Gates <nick@nickgates.com>
@gatesn gatesn added the changelog/fix A bug fix label Oct 26, 2026
@gatesn
gatesn enabled auto-merge (squash) October 26, 2026 19:27
@gatesn
gatesn merged commit 50303c1 into develop Oct 26, 2026
108 of 110 checks passed
@gatesn
gatesn deleted the ngates/datafusion-statistics-precision branch October 26, 2026 19:33
@codspeed

codspeed Bot commented Oct 26, 2026

Copy link
Copy Markdown

Merging this PR will regress 3 benchmarks

4 warnings, 1 note

⚠️ Walltime results may be unreliable

Some benchmarks used the Walltime instrument outside CodSpeed Macro Runners, which can make the results inconsistent.

Learn more about Macro Runners

See affected benchmarks

⚠️ Unable to measure the execution of 2 benchmarks

These benchmarks measured no execution time, so their results are not comparable and count as unchanged. This usually happens when the compiler removes the code under test.

Prevent compiler optimizations

See affected benchmarks

⚠️ 18 benchmarks are dominated by system calls

System calls cannot be simulated consistently and are left out of the measure. The reported value understates the real cost. Switch to the Walltime instrument to measure them.

Learn more about system calls

See affected benchmarks

⚠️ Base and head ran on different runner types

Some benchmarks with significant performance changes were compared across different runner types, so the changes might not come from the code. Run base and head on the same runner type, or use CodSpeed Macro Runners for more stable results.

Learn more about Macro Runners

Open the report in CodSpeed to investigate

ℹ️ 40 benchmarks have no flamegraph

The flamegraph wasn't generated: the symbols of the profiling trace could not be resolved, because no information about the language frames was collected.

See affected benchmarks

⚡ 4 improved benchmarks
❌ 3 regressed benchmarks
✅ 2432 untouched benchmarks
⏩ 12 skipped benchmarks1

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

Mode Benchmark BASE HEAD Efficiency
❌ CPU Simulation chunked_dict_primitive_canonical_into[f64, (1000, 1000, 10)] 146.6 µs 200.9 µs -27.03%
❌ CPU Simulation test_repeated_scan_scalar_at[int_str_float] 474.6 µs 556.1 µs -14.66%
❌ CPU Simulation test_scan_filter[int] 3 ms 3.4 ms -11.41%
⚡ CPU Simulation bench_compare_sliced_dict_primitive[(3333, 10000)] 71.1 µs 32.9 µs ×2.2
⚡ Walltime threshold_neon[8] 1.9 µs 1.4 µs +42.25%
⚡ Walltime threshold_neon[64] 3.5 µs 2.6 µs +32.98%
⚡ Walltime threshold_neon[80] 4.2 µs 3.4 µs +24.03%

Tip

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


Comparing ngates/datafusion-statistics-precision (2993291) with develop (4d0eccd)

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog/fix A bug fix

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants