You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Python interface would probably lead to the greatest improvements, but needs more work to make our mathematical formulation more general (I.e. not written for Pyomo). However, the persistent solver could be a 'quick' fix for models that end up making small changing and then re-solving (cf. SPORES).
This issue can be used to track any updates in Gurobi solver interfaces.
The text was updated successfully, but these errors were encountered:
The first two model runs (cost optimal and spore 0) build a fresh model in Gurobi. It takes approximately 2-3x longer for Pyomo to send the model to Gurobi on a fresh build (~15s instead of ~6s), so GurobiPersistent is probably only worthwhile when n_spores > 3.
We want to interface with Gurobi more directly, to leverage performance improvements in the solver backend.
One method is to use the Gurobi Python interface
Another method is the Pyomo Gurobi persisent solver (usage documentation)
The Python interface would probably lead to the greatest improvements, but needs more work to make our mathematical formulation more general (I.e. not written for Pyomo). However, the persistent solver could be a 'quick' fix for models that end up making small changing and then re-solving (cf. SPORES).
This issue can be used to track any updates in Gurobi solver interfaces.
The text was updated successfully, but these errors were encountered: