Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Enhancement]explicit specific arrow use avx2 as default #51038

Merged
merged 1 commit into from
Sep 19, 2024

Conversation

zombee0
Copy link
Contributor

@zombee0 zombee0 commented Sep 14, 2024

Why I'm doing:

Hitherto, we use default configuration of arrow, which means ARROW_SIMD_LEVEL=SSE4_2
and ARROW_RUNTIME_SIMD_LEVEL=MAX, there are two issues, 1. avx2 may have better
performance, 2. even arrow specific SSE4_2 as default compile configuration, it uses xsimd
which use avx512 as default configuration, and because the ARROW_RUNTIME_SIMD_LEVEL=MAX
in some case, the performance is bad.

What I'm doing:

Fixes #issue

What type of PR is this:

  • BugFix
  • Feature
  • Enhancement
  • Refactor
  • UT
  • Doc
  • Tool

Does this PR entail a change in behavior?

  • Yes, this PR will result in a change in behavior.
  • No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

  • Interface/UI changes: syntax, type conversion, expression evaluation, display information
  • Parameter changes: default values, similar parameters but with different default values
  • Policy changes: use new policy to replace old one, functionality automatically enabled
  • Feature removed
  • Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

  • I have added test cases for my bug fix or my new feature
  • This pr needs user documentation (for new or modified features or behaviors)
    • I have added documentation for my new feature or new function
  • This is a backport pr

Bugfix cherry-pick branch check:

  • I have checked the version labels which the pr will be auto-backported to the target branch
    • 3.3
    • 3.2
    • 3.1
    • 3.0
    • 2.5

@zombee0 zombee0 requested a review from a team as a code owner September 14, 2024 07:12
@github-actions github-actions bot added the 3.3 label Sep 14, 2024
@zombee0
Copy link
Contributor Author

zombee0 commented Sep 18, 2024

@mergify rebase

Copy link
Contributor

mergify bot commented Sep 18, 2024

rebase

❌ Unable to rebase: user zombee0 is unknown.

Please make sure zombee0 has logged in Mergify dashboard.

Copy link

[Java-Extensions Incremental Coverage Report]

pass : 0 / 0 (0%)

Copy link

[FE Incremental Coverage Report]

pass : 0 / 0 (0%)

Copy link

[BE Incremental Coverage Report]

pass : 0 / 0 (0%)

@wangruin wangruin merged commit 1f4e238 into StarRocks:main Sep 19, 2024
43 checks passed
Copy link

@Mergifyio backport branch-3.3

@github-actions github-actions bot removed the 3.3 label Sep 19, 2024
Copy link
Contributor

mergify bot commented Sep 19, 2024

backport branch-3.3

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Sep 19, 2024
Copy link

@Mergifyio backport branch-3.3

Copy link
Contributor

mergify bot commented Sep 19, 2024

backport branch-3.3

✅ Backports have been created

Copy link

@Mergifyio backport branch-3.3

Copy link
Contributor

mergify bot commented Sep 19, 2024

backport branch-3.3

✅ Backports have been created

Copy link

@Mergifyio backport branch-3.3

Copy link
Contributor

mergify bot commented Sep 19, 2024

backport branch-3.3

✅ Backports have been created

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants