Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: new job default time limits based on historic runtime

...

QoS nameTypeSuitable for...Shared nodes Maximum jobs per userDefault / Max Wall Clock LimitDefault / Max CPUsDefault / Max Memory
nffractionalserial and small parallel jobs. It is the defaultYes-6 hours average runtime + standard deviation / 2 days1 / 648 GB / 128 GB
niinteractiveserial and small parallel interactive jobsYes112 hours / 7 days1 / 328 GB / 32 GB
npparallelparallel jobs requiring more than half a nodeNo-6 hours average runtime  + standard deviation / 2 days-240GB / 240 GB per node (all usable memory in a node)

...

QoS nameTypeSuitable for...Shared nodes Maximum jobs per userDefault / Max Wall Clock LimitDefault / Max CPUsDefault / Max Memory
effractionalserial and small parallel jobs - ECGATE serviceYes-12 hours average job runtime + standard deviation / 2 days1 / 88 GB / 16 GB
eiinteractiveserial and small parallel interactive jobs - ECGATE serviceYes112 hours  / 7 days1 / 48 GB / 8 GB
ellongserial and small parallel interactive jobs - ECGATE serviceYes-12 hours average job runtime + standard deviation  / 7 days1 / 88 GB / 16 GB
etTime-critical Option 1

serial and small parallel Time-Critical jobs.

Only usable through ECACCESS Time Critical Option-1

Yes-12 hours average job runtime + standard deviation  / 12 hours1 / 88 GB / 16 GB


Info
titleTime limit management

See HPC2020: Job Runtime Management for more information on how the default Wall Clock Time limit is calculated.


Note
titleLimits are not set in stone

Different limits on the different QoSs may be introduced or changed as the system evolves.


Tip
titleChecking QoS setup

If you want to get all the details of a particular QoS on the system, you may run, for example:

No Format
sacctmgr list qos names=nf
Note
titleWork in progress
Different limits on the different QoSs may be introduced or changed as the system evolves to its final configuration.


Submitting jobs remotely

If you are submitting jobs from a different platform via ssh, please use the *-batch dedicated nodes instead of the *-login equivalents:

...