-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Documenting building with simd feature #882
Comments
I am probably doing something wrong and/or we need better docs around this |
I think you need the nightly channel to use simd, as packed_simd requires
nightly.
β¦On Sat, Aug 14, 2021, 15:23 Andy Grove ***@***.***> wrote:
I am probably doing something wrong and/or we need better docs around this
β
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#882 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAVE476BBDW7CIC4CIG3E73T4Z37PANCNFSM5CFEPPIQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>
.
|
|
I changed the issue to add some docs around this. Btw, @andygrove AFAIK the SIMD option doesn't help a lot with the TPC-H queries. Building with snmalloc or mimalloc and fat LTO (longer build time) does improve execution times. |
It would be good if we can provide doc on how to produce the most optimized build: simd + snmalloc + LTO. |
I also think we should suggest building with |
Here is an example of using all the options: https://github.com/h2oai/db-benchmark/pull/182/files |
Hello. I could try this. To confirm - is the idea to add docs just for SIMD? Or for the most optimized build? |
I would love to have docs for the most optimized build, but we can start with SIMD if that's too much :) |
Describe the bug
To Reproduce
Run command above.
The text was updated successfully, but these errors were encountered: