bvolpato opened a new pull request, #26837:
URL: https://github.com/apache/datafusion/pull/26837

   > [!IMPORTANT]
   >
   > **Fork CI setup:** For pull requests from a fork to `main`, enable 
workflows in your fork's **Actions** tab before you push.
   > See the [fork CI setup 
guide](https://datafusion.apache.org/contributor-guide/#pull-requests-from-forks).
   
   ## Which issue does this PR close?
   
   Part of #13813.
   
   ## Rationale for this change
   
   Criterion's `--test` mode still builds and sorts the full benchmark 
fixtures. In this [merge-queue 
job](https://github.com/apache/datafusion/actions/runs/40614324735/job/122573148419),
 the sort-axis cases consumed about 162 seconds of benchmark execution. The 
microbenchmark smoke job was the longest extended check in the sampled runs.
   
   ## What changes are included in this PR?
   
   Set `SORT_AXIS_ROWS=200000` in the microbenchmark CI command. The sort-axis 
benchmarks accept that override and label the selected size. Full performance 
runs retain the existing 1M-row default.
   
   Every key, cardinality, payload-width, and ordering combination remains 
enabled. The smoke input still spans multiple batches and exceeds the default 
in-place threshold in raw integer-key payload alone.
   
   ## What is the testing strategy for this PR?
   
   The existing xtask command snapshot was updated and passes. Paired 
`ci-bench` smoke runs of the sort target took 357s at the full input size and 
139s with the cap, excluding compilation. These are single runs on a shared 
Linux host.
   
   Formatting, all-target/all-feature Clippy, and the extended workspace suite 
passed. Full workspace validation included the RSS sampling prerequisite 
already carried in #26445.
   
   ## Are there any user-facing changes?
   
   CI smoke inputs are smaller. Normal performance benchmarks keep their 
existing default input size.
   
   AI-assisted contribution.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to