haohuaijin opened a new pull request, #11498: URL: https://github.com/apache/arrow-rs/pull/11498
Trim selector lengths, column counts and string lengths, and remove the duplicate int32 type profile. Use a two-second warmup and 50 samples while retaining the default measurement time. # Which issue does this PR close? - follow up #11389 # Rationale for this change <!-- Why are you proposing this change? If this is already explained clearly in the issue then this section is not needed. Explaining clearly why changes are proposed helps reviewers understand your changes and offer better suggestions for fixes. Please try to explain the problem you are trying to solve in terms of the user-visible behavior, rather than the implementation. --> The `row_selection_cursor` benchmark matrix contains 1,140 cases, making a full run expensive. Reduce the parameter combinations while retaining all four selection distributions, both input backings, and all three execution policies. # What changes are included in this PR? <!-- There is no need to duplicate the description in the issue here but it is sometimes worth providing a summary of the individual changes in this PR. --> Reduce the matrix from 1,140 to 288 cases: - Keep average selector lengths `[4, 28, 32, 40]`, covering fragmented selections and values around the default Auto threshold of 32. - Keep column counts `[2, 8, 32]`. - Keep Utf8View lengths `[8, 16, 256]`, covering inline, short non-inline, and longer strings. - Remove `dtype/int32`, which duplicates the baseline Int32 input. Set the warmup time to 2 seconds and the sample size to 50. Retain the default 5-second measurement target. # Are these changes tested? <!-- We typically require tests for all PRs in order to: 1. Prevent the code from being accidentally broken by subsequent changes 2. Serve as another way to document the expected behavior of the code If tests are not included in your PR, please explain why (for example, are they covered by existing tests, if so identify these tests)? If this PR claims a performance improvement, please include evidence such as benchmark results. DO NOT simply paste a list of commands ran to verify the code; this is what our CI is for and it pollutes the PR. ONLY explain if testing was included with this PR, or why it wasn't. --> # Are there any significant user-facing changes? <!-- Significant user-facing changes include: - Breaking public API change - Significant change to existing functionality (e.g. function returns something different) These need to be explicitly called out to ensure we have proper documentation if required and to ensure we follow proper semantic versioning. DO NOT restate the changes of this PR; if a bug was fixed and already explained above, we don't need this to be restated as a user-facing change. --> -- 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]
