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.

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

[README] add note on thread-safety #226

Merged
merged 1 commit into from
Jun 28, 2023
Merged

[README] add note on thread-safety #226

merged 1 commit into from
Jun 28, 2023

Conversation

odow
Copy link
Member

@odow odow commented Jun 28, 2023

Closes #225

cc @Zinoex is this sufficient?

@Zinoex
Copy link

Zinoex commented Jun 28, 2023

Yep. Thanks!

It would be interesting to have thread safe version (spawning a new process?) at some point, but for now this is good.

@odow
Copy link
Member Author

odow commented Jun 28, 2023

It would be interesting to have thread safe version

Just use a different optimizer that is thread-safe. In almost all cases, you should be using HiGHS instead of GLPK.

@odow odow merged commit 57041ce into master Jun 28, 2023
8 checks passed
@odow odow deleted the odow-patch-1 branch June 28, 2023 21:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

GLPK does not support multithreading (non-reentrant)
2 participants