CPLEX finds what appears to be the optimal solution fairly quickly in both models. If you compare the first two columns (Node and Nodes Left), you will see that CPLEX needs more time per node when you add the cuts than when you do not. That's not entirely surprising, since you added over 12,000 cuts. Your hope in adding cuts is that they will tighten the lower bound enough to let CPLEX prune nodes earlier and process fewer total nodes. That could still happen if you let both version run to completion. As of the one hour mark, however, CPLEX has processed around 59,000 nodes in the run with cuts versus around 81,000+ nodes without the cuts, which helps explain the superior lower bound.
At the one hour mark, the run with cuts has about 78% of visited nodes still alive versus about 81% still alive in the run without cuts. So the cuts are having some effect, but arguably not enough to justify their use.
------------------------------
Paul Rubin
Professor Emeritus
Michigan State University
------------------------------