Update JuMP and linopy benchmark scripts #163
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey! I've been meaning to check this project out. People keep mentioning it to me.
Your docs are very nice, and I quite like this style of modeling. I couldn't get the benchmarks to run (told me it couldn't find
ortools-python
and it took ages to try and find a feasible install?), but here are a couple of minor changes. (Feel free to close this PR if you would prefer to keep them as-is.)I thought it might be helpful to explain why JuMP's memory usage is so high: we actually store three copies of the problem data.
x
andy
variablesHere's a demonstration:
Biggest change with
direct_model
is that memory usage drops by 20% (not the expected 1/3 because there's some other overhead, etc).If we turn off passing variable names to Gurobi, we get more improvement:
But I wouldn't expect most users to care about this.