Skip to content
This repository has been archived by the owner on May 4, 2021. It is now read-only.

Use multiprocessing instead of fork. #97

Open
Joelgranados opened this issue Oct 1, 2014 · 2 comments
Open

Use multiprocessing instead of fork. #97

Joelgranados opened this issue Oct 1, 2014 · 2 comments
Assignees
Labels

Comments

@Joelgranados
Copy link
Contributor

In timestream/manipulate/pipecomponets.py:(PlantExtractor) there was a comment that multiprocessing must be used instead of os.fork.

Putting it here so we don't loose track of the discussion. And I removed the comment from the code.

@Joelgranados
Copy link
Contributor Author

Why should we prefer multiprocessing?

@Joelgranados
Copy link
Contributor Author

I remember why I chose os.fork instead of multiprocessing:
We have to be hacky if we want to use multiprocessing with classes.
http://stackoverflow.com/questions/17172878/using-pythons-multiprocessing-process-class
http://www.rueckstiess.net/research/snippets/show/ca1d7d90

If you want to implement it in multiprocessing, that beast is all yours :)

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

No branches or pull requests

2 participants