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

Use processes instead of threads for the portfolio solver #206

Open
amaleewilson opened this issue Mar 10, 2021 · 0 comments
Open

Use processes instead of threads for the portfolio solver #206

amaleewilson opened this issue Mar 10, 2021 · 0 comments
Assignees
@amaleewilson

Comments

@amaleewilson
Copy link
Collaborator

The current implementation using threads results in waster resources because the threads running the solvers cannot be stopped at any time. See the discussion in #185. The portfolio solver should spawn child processes instead.
amaleewilson added a commit that referenced this issue Mar 10, 2021
@amaleewilson
Add portfolio solving. (#185)
15f796b 
This adds a PortfolioSolver that uses threads for the solvers. A future version should use processes instead, as mentioned in #206
@amaleewilson amaleewilson self-assigned this Mar 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@amaleewilson amaleewilson

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@amaleewilson