As far as I can tell, Gurobi can only be asked to report elapsed times. Except in certain situations (you are running a primal or dual simplex method on a continuous linear program, you have limited Gurobi to a single thread by specifying the "threads=1" directive, you have a very old single-core computer) Gurobi runs multiple threads in parallel, with the result that it is hard to find a meaningful "CPU time" to report. In particular the AMPL _solve_time may be the sum of the CPU times on all cores, which is a misleading measure of how long Gurobi took to solve the problem.
Bob Fourer
From: am...@googlegroups.com [mailto:am...@googlegroups.com]
On Behalf Of tolentin...@gmail.com
Sent: Tuesday, July 2, 2013 2:21 PM
To: am...@googlegroups.com
Subject: [AMPL 7223] AMPL/GUROBI: How to Limit "CPU Time" instead of "ELAPSED time"