Originally posted by: SystemAdmin
What you are looking for is called a
MIP start.
In your case CPLEX should already use MIP starts automatically: it keeps all solutions it finds as a MIP start for a potential next run. When the second solve is started you should see log messages like
MIP start 'm1' defined solution with objective ...
This shows that CPLEX used a solution from a previous run as warm start for this solve.
In your case you could also try to record the cuts that CPLEX finds (this can only be done with the callable library and is described in several threads on this Forum) and explicitly add them to the second problem. If that will improve performance highly depends on the problem data.
Or you could try to at least query the number of cuts of each type (there are functions to do that) and disable in the second run those types of cuts for which CPLEX did not find/use any cuts in the first run. Again, the effect of this may be problem dependent.
#CPLEXOptimizers#DecisionOptimization