...
Jobs have a 'max_cpus' value which puts an upper limit on how wide a single job can expand. This value can be supplied via a site-wide default or specified on a job-by-job basis.
...
SmartShare
...
Disabling SmartShare
To opt out, the site administrator can set the supervisor_smart_share_mode to "none" in qb.conf on the supervisor machine:
| Code Block |
|---|
supervisor_smart_share_mode = none
|
SmartShare from a user's perspective
...
| Excerpt |
|---|
Configuring SmartShare | Tip |
|---|
SmartShare is automatically enabled for new 6.6+ installs and upgrades alike. Disabling SmartShareTo opt out, the site administrator can set the supervisor_smart_share_mode to "none" in qb.conf on the supervisor machine: | Code Block |
|---|
supervisor_smart_share_mode = none
|
|
- supervisor_smart_share_mode
- Can be either “jobs” or “none”.
- default: "jobs"
- Setting it to “jobs” will make the system try to balance the number of the automatically-expanded “secondary" instances on a job-to-job basis
- Setting it to “none” disables SmartShare.
- supervisor_smart_share_preempt_policy
- method of preemption for secondary instances
- aggressive, passive, disabled
- default: aggressive
- supervisor_default_max_cpus
- used to set the site-wide default value of “max_cpus” if not given at submission
- default: -1
- Note: “*” can be used in the qb.conf file too, instead of -1
- supervisor_max_cpus_limit
- largest value of “max_cpus” that can be used on any job
- default 100
- Note: if any job specifies a value greater than this, the system will silently cap it to this value
|
...