Jump to content
  • Announcements

    • admin

      PBS Forum Has Closed   06/12/17

      The PBS Works Support Forum is no longer active.  For PBS community-oriented questions and support, please join the discussion at http://community.pbspro.org.  Any new security advisories related to commercially-licensed products will be posted in the PBS User Area (https://secure.altair.com/UserArea/). 

How to limit the maximum number of processors per job

Recommended Posts



max_run_res.ncpus just based on users, or groups, or project


Wondering how to limit the max. cpus per job  ?



For example,   just can request  Max. 168 CPUs per job.



Appreciating your time







Share this post

Link to post
Share on other sites

max_run_res.<res> can be applied to generic user, generic group, generic project, named user, named group, named project, and/or overall (o:PBS_ALL). 


Since you want to impose the limit of ncpus per job, I am assuming that you don't want to limit to restrict the total ncpus that could be running or queued. IOW, UserA could submit three 168ncpus jobs, and the three jobs would be eligible to run if there were enough resources available.


If this is true, then my suggestion would be to introduce a queuejob event hook that validates the total ncpus being requested is less than the maximum you want set. In addition, the same logic would be used for the modifyjob event hook. This way the user would not be able to change the total ncpus to something larger after the job was successfully submitted. 

Share this post

Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in

Sign In Now