-
Notifications
You must be signed in to change notification settings - Fork 193
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
Use 4x more threads for FFTW #1120
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1120 +/- ##
==========================================
+ Coverage 55.78% 57.31% +1.53%
==========================================
Files 171 162 -9
Lines 4005 3882 -123
==========================================
- Hits 2234 2225 -9
+ Misses 1771 1657 -114
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moar speed
@glwagner, should FourierFlows.jl be doing this also? |
I think it's irrelevant if you aren't also using julia's built-in multithreading. But FourierFlows could use it as a default in case any subidiary models use multithreading at some point. |
9db165f
to
b37aef4
Compare
b37aef4
to
eb994d2
Compare
Ran some multithreading benchmarks on Tartarus and Satori but the results weren't really different from previous benchmarks. Perhaps it's still good to merge in case this PR improves performance on other machines? Multithreading on Tartarus
Multithreading on Satori
|
Hmmm, using 2 threads seems to allocate the most memory by far. Seems pretty weird. |
Wait... were these benchmarks with the latest commit from this PR? |
Ah sorry I had the old benchmarks open in a different tab and forgot to copy paste them here: #869 (comment)
|
Resolves #1113
Needs new multi-threading benchmarks. Will do as part of #1088 (need to add nice multithreading benchmark script on
ar/benchmarks
branch).