JasonLi-cn opened a new pull request, #9732:
URL: https://github.com/apache/arrow-datafusion/pull/9732
## Which issue does this PR close?
<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases. You can
link an issue to this PR using the GitHub syntax. For example `Closes #123`
indicates that this PR will close issue #123.
-->
Closes #.
## Rationale for this change
optimize `concat` and `concat_ws` function.
### Benchmark(only concat)
```shell
Gnuplot not found, using plotters backend
concat function/concat(old)/1024
time: [91.400 µs 93.575 µs 96.505 µs]
Found 10 outliers among 100 measurements (10.00%)
5 (5.00%) high mild
5 (5.00%) high severe
concat function/concat(new)/1024
time: [18.160 µs 18.192 µs 18.230 µs]
Found 12 outliers among 100 measurements (12.00%)
1 (1.00%) low mild
4 (4.00%) high mild
7 (7.00%) high severe
concat function/concat(old)/4096
time: [88.002 µs 88.087 µs 88.185 µs]
Found 8 outliers among 100 measurements (8.00%)
1 (1.00%) low mild
7 (7.00%) high severe
concat function/concat(new)/4096
time: [18.303 µs 18.407 µs 18.538 µs]
Found 4 outliers among 100 measurements (4.00%)
3 (3.00%) high mild
1 (1.00%) high severe
concat function/concat(old)/8192
time: [88.308 µs 88.534 µs 88.798 µs]
Found 5 outliers among 100 measurements (5.00%)
2 (2.00%) high mild
3 (3.00%) high severe
concat function/concat(new)/8192
time: [18.229 µs 18.310 µs 18.413 µs]
Found 16 outliers among 100 measurements (16.00%)
5 (5.00%) high mild
11 (11.00%) high severe
```
### Attention
For the purpose of benchmarking, I haven't officially replaced the `concat`
and `concat_ws` function yet. If the community finds this PR meaningful, I will
proceed with the replacement.
## 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.
-->
## 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)?
-->
## Are there any user-facing changes?
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->
--
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]
