Gurobi Remote Services Parameters
As noted in the Quick Start Guide, you start Gurobi Remote Services by
grb_rs program on the server machine. This starts
a Windows service on Windows systems, and a daemon on Linux or Mac OS
systems. When Gurobi Remote Services starts, it picks up user
parameter settings from an optional
grb_rs.cnf file (the file
must be in the directory that contains the
To modify the default settings, you should place a list of
parameter=value lines in this configuration file. Lines that
begin with the # symbol are treated as comments and are ignored.
Here's an example file:
# Configuration file PASSWORD=abcd1234 ADMINPASSWORD=1234abcdYou can create this file using your favorite text editor (
Notepadis a good choice on Windows).
Some Gurobi Remote Services parameters are generic, while others are specific to a particular service. The generic parameters are:
- The password that the client program must supply in order to submit a job. Note that all user data is passed between the client and server using 256-bit AES encryption, whether you supply a password or not. The server password simply prevents unauthorized clients from submitting jobs to the server. The default is no password.
- The password for performing administrative tasks.
This is different from the password that client programs must
provide. Administrative tasks are performed using the
gurobi_clprogram. Example tasks include changing the job limit and killing jobs (details will follow). Note that the administrator password must be set if you wish to enable remote administration.
- A limit on the number of threads a single job can launch on the server. By default, a job can create as many threads as it likes (although by default the Gurobi algorithms won't create more than one thread per core).
A few Gurobi Remote Services parameters are specific to Compute Server. They control the job queuing features...
- A limit on the number of client jobs that are allowed to run on the server at a time. Client requests beyond this limit are queued. The default limit is 2.
- A hard limit on the number of simultaneous client
jobs. Certain jobs (those with priority 100) are allowed to ignore
JOBLIMIT, but they aren't allowed to ignore this limit. Client requests beyond this limit are queued. The default hard limit is 100.
- When set to 1, the server ignores user job priorities.
The configuration file is only read once, when Gurobi Remote Services first starts. Subsequent changes to the file won't affect parameter values on a running server.