Repository navigation
Reuse deserialized segments across partial V2 scans - #10849
joseph-isaacs wants to merge 1 commit into
Performance Gate Passed
4 warnings, 1 note
⚠️ Walltime results may be unreliableSome benchmarks used the Walltime instrument outside CodSpeed Macro Runners, which can make the results inconsistent.
⚠️ Unable to measure the execution of 2 benchmarksThese 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.
⚠️ 17 benchmarks are dominated by system callsSystem 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.
⚠️ Base and head ran on different runner typesSome 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.
ℹ️ 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.
⚡ 4 improved benchmarks
✅ 2435 untouched benchmarks
⏩ 12 skipped benchmarks1
Performance Changes
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ⚡ | CPU Simulation | test_scan_filter_to_arrow_array[int_float] |
4 ms | 3.5 ms | +15.85% |
| ⚡ | CPU Simulation | test_repeated_scan_filter[int_float] |
3.8 ms | 3.4 ms | +12.58% |
| ⚡ | CPU Simulation | test_repeated_scan_filter[int] |
2.7 ms | 2.4 ms | +11.65% |
| ⚡ | CPU Simulation | test_scan_filter_to_arrow_array[int] |
2.8 ms | 2.5 ms | +11.15% |
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/v2-no-dynamic-profile-10799 (a5e4a99) with develop (a59294e)
Footnotes
-
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. ↩