-
Notifications
You must be signed in to change notification settings - Fork 3
Use mpiexec only for parallel execution #264
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
Conversation
|
As an internal reference - the benchmark from @ligerzero-ai : https://github.com/orgs/pyiron/discussions/211#discussioncomment-8034046 |
|
@XzzX just for your awareness: I am currently benchmarking the Executor we use inside |
|
The benchmark is now included in the continuous integration setup. |
OpenMPIMPIch |
Sure, get it done this week (hopefully) |
@ligerzero-ai based on your performance analysis I designed a small benchmark. Using this benchmark I found the bug that is fixed with this pull request. The updated results of the benchmark are posted below. Now
pympipoolis competitive with theProcessPoolExecutor. Can you test this branch with your own benchmark?Code
Results
python benchmark.py staticpython benchmark.py processpython benchmark.py threadmpiexec -n 4 python -m mpi4py.futures benchmark.py mpi4pypython benchmark.py pympipoolflux start; python benchmark.py flux