-
Notifications
You must be signed in to change notification settings - Fork 35
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
JuMP.value() Performance Issue #204
Comments
You can try a fix with |
Thanks a lot @odow ! |
No problem. If you're solving large MIPs, you should also try out HiGHS.jl: https://github.com/jump-dev/HiGHS.jl |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When solving a big MIP using Cbc and JuMP, the time to retrieve the values of all variables seems to grow with the square of the problem size.
Probing the entire solution of the following mock problem takes 0.07s for M=1, 7.0s for M = 10 and 700s for M =100 in my laptop.
When M=1000, it takes 19 hours to get all primal values from this model. Just by comparison, the same operation takes only 62s when using Gurobi.jl as optimizer with M=1000 in the same machine.
Any insights on how can I tackle this problem, or any alternative ways to retrieve solution values in big models?
Thanks!
The text was updated successfully, but these errors were encountered: