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.
This option is very useful if model building becomes a bottleneck.
I tested with the case: https://github.com/jump-dev/open-energy-modeling-benchmarks/tree/main/TulipaEnergyModel/cases/1_EU_investment_simple
And considered a 744-hour window.
After running:
Which is a 30% speedup.
I can imagine some names are important for model interaction.
The more complicated version with names would be to generate names after the build, and only on the need basis.
A simpler version would be to only enable names of specific variables and constraints that are more frequently used.
The latter can be done by calling the JuMP function right before and right after each group of constraints / variables.