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.

Sign up for GitHub

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

Jump to bottom

Replacing python_utilities.parallel #65

Open
sethaxen opened this issue Jun 2, 2022 · 1 comment
Open

Replacing python_utilities.parallel #65

sethaxen opened this issue Jun 2, 2022 · 1 comment

Comments

@sethaxen
Copy link
Collaborator

sethaxen commented Jun 2, 2022 •
edited
Loading

python_utilities.parallel has always been a bit of a hack to have a unified API for 4 parallelization approaches: serial, distributed, multithreaded, and message passing. It would be better to call that functionality from a better tested and maintained package, but I have until now been unable to find one. It looks like Ray might have this functionality. Their API is quite different, so it would take a little work to switch us over to their API.
@sethaxen
Copy link
Collaborator Author

sethaxen commented Jun 3, 2022

Alternatively, mpi4py.futures.MPICommExecutor is a child of concurrent.futures.Executor, so we could perhaps just use Executor API functions to support all 4 modes. I don't see a SequentialExecutor or SerialExecutor anywhere, so we may need to roll our own.

@sethaxen sethaxen changed the title Replacing python_utilities.parallel with ray Replacing python_utilities.parallel Jun 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sethaxen