The Gurobi Optimizer provides the option to record the set of Gurobi commands issued by your program and store them to a file. The commands can be played back later using the Gurobi Command-Line Tool. If you replay the commands on a machine with the same specs (operating system, core count, and instruction set) as the machine where you created the recording, your Gurobi calls will take the exact same computational paths that they took when you ran your original program.
Recording can be useful in a number of situations.
Recording is useful for testing across deployment scenarios. In particular, you can do the following:
localhost:61000
; this can be overridden by setting the
GRB_COMPUTESERVER
environment variable. If
GRB_COMPUTESERVER
is set to an empty string, the replay will
occur locally.
GRB_COMPUTESERVER
has priority over
GRB_CSMANAGER
. If GRB_CSMANAGER
is set to "", the
replay will run locally or on the specified Compute Server.
GRB_CLOUDACCESSID
and GRB_CLOUDSECRETKEY
will run the replay on the cloud.
GRB_COMPUTESERVER
has priority over GRB_CLOUDACCESSID
(and GRB_CLOUDSECRETKEY
). If GRB_CLOUDACCESSID
is set to "",
the replay will run locally or on the specified Compute Server.
localhost
(with the default port
41954). This can be overridden by setting the GRB_TOKENSERVER
environment variable. If GRB_TOKENSERVER
is set to an empty
string, the replay will be done using a local license.
WorkerPool
parameter
(used in the distributed MIP and distributed concurrent algorithms)
can only be done by setting the GRB_WORKERPOOL
environment
variable.