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/). 


  • Content count

  • Joined

  • Last visited

  1. using server_dyn_res

    Hi Scott Thanks for your reply. And thanks for the point to a different community forum. So if I understand you correctly in your scenario, then if instead each job used foo_widget=2 then if you had 50 jobs in the queue 25 would run in the first pass of the scheduler, if the script returned 50. Then another 25 would run the next pass if the script returned 50 again. And if I'm correct each job is only processed once per scheduler cycle so if the job finished really quickly a new one would not start during that pass (ie the usage of foo_widget would not be decreased by 2)? Just to give you some background what I'm doing: we are using pbs pro do govern approval for our vCloud requests. We queue up all the requests and then approve thouse that we have enough resources. So we have a scripts which obtains cpu and memory and assign to server_dyn_res variables and each approval passes its usage a resource requirements. As such we would like to allow as many approvals as we can without over subscribing. cheers, Jakub
  2. using server_dyn_res

    I'm using server_dyn_res variables to track if a job should run. This is working fine but I would like to be able to run multiple jobs per scheduler iteration. Does PBS increase the values of the variables using the entries set in each job, or do I have to continue only running one job at a time. Thanks Jakub