You may have observed this parameter in the tuner output from a compute server or with distributed tuning. Gurobi uses two closely related parameters to control whether nodefiles can be written to disk when solving on a Compute Server:
-
NO_LOCAL_DISK(server parameter)
This is a server-side configuration setting defined in the Compute Server configuration file. It determines whether nodefiles can be written at all on that server.
IfNO_LOCAL_DISK=1, no job running on that server is permitted to write nodefiles, regardless of any client-side settings. -
GURO_PAR_NOLOCALDISK(client parameter)
This is a job-level parameter that provides additional control. Even if the server allows local disk usage (NO_LOCAL_DISK=0), settingGURO_PAR_NOLOCALDISK=1can forbid nodefile writing for specific jobs, effectively overriding the server’s allowance.
You may observe this parameter in tuner output from a Compute Server or during distributed tuning. It indicates whether the current job has permission to write to local disk.
Behavior Overview
Server Setting (NO_LOCAL_DISK) |
Client Setting (GURO_PAR_NOLOCALDISK) |
Nodefile Writing Allowed? |
|---|---|---|
| 0 (allowed) | 0 (allowed) | Yes |
| 0 (allowed) | 1 (forbidden) | No (job-level override) |
| 1 (forbidden) | any | No (server restriction) |
-
GURO_PAR_NOLOCALDISKis a hidden parameter mainly used for internal reporting and job-level restrictions. - When active (
=1), it automatically resets disk-related parameters such asNodeFileStartto their defaults. - This parameter does not affect the solving process itself; it is a disk usage restriction enforced either by the server or client.
- You can use
NO_LOCAL_DISKto manage global disk policies, while users or client processes may applyGURO_PAR_NOLOCALDISKto selectively restrict disk use for individual jobs.
Further Information