Originally posted by: EdKlotz
Please upload the node log of the run. Paul's comments about near symmetry could indeed explain the lack of progress in the best bound. I have a few suggestions to try based on the thread so far.
1) Try running with default MIP emphasis and default variableselect along with the other parameters you currently use. Variableselect 3 can be effective, but it also slows down the rate of node throughput. Maybe you can start to make more progress in the best bound if CPLEX can simply process more nodes.
2) Instead of solution polishing to make progress in the incumbent, try periodically applying the RINS heuristics, say every 100-200 nodes. This is a local search heuristic, and based on your description of the model, it may be effective at improving on existing solutions.
3) Try running with all cuts set to 2 and probing set to 3. Those settings can help move the best bound faster.
4) If the costs are similar, try creating a different version of the model where the costs are the same, and solve that, possibly with aggressive symmetry detection. If that model solves much faster, that result helps you in two ways. First, it confirms that the slight differences are in play regarding the challenging aspect of the model. Second, you can take the optimal solution from this easier model and use it as a MIP start for the version with slightly different costs. Given that you quoted a gap of 40%, I wouldn't be surprised if this gave you a better solution.
5) Try creating a smaller version of this model with the same characteristics so you can do more tests in less time.
6) Have a look at the paper and presentation here:
https://www.ibm.com/developerworks/community/blogs/jfp/entry/practical_guidelines_for_solving_difficult_mixed_integer_programs?lang=en
for some general tactics on getting better MIP performance.
#CPLEXOptimizers#DecisionOptimization