Author Topic: limit number of workers, not just number of cpus  (Read 3532 times)

jesse

  • Sr. Member
  • ****
  • Posts: 40
limit number of workers, not just number of cpus
« on: August 19, 2008, 02:18:59 AM »
We have a farm of 20 worker nodes and 160 cpus.  We have a plugin that can only run on 5 worker nodes at one time.  Is it possible to limit the number of workers that the job will get sent to at one time?  I've seen the cpus restriction, but it does not see that this will work well enough. 

I know I have the following options, but I was hoping for a better solution:
  • Limit the number of cpus to 5, thus insuring that only 5 workers would ever work on the job.  Sadly this would lose 35 potential procs.
  • Explicit run on 5 specific workers.  This would be painful if the wrong workers were chosen at submission time wherein 5 nodes might be free, but the wrong 5.

Any Help would be appreciated.
Cheers,
jesse

jesse

  • Sr. Member
  • ****
  • Posts: 40
Re: limit number of workers, not just number of cpus
« Reply #1 on: August 19, 2008, 06:05:16 AM »
I've now read more of the Administration pdf.  I see that clusters might be useful in this case.  Is it possible to limit a job to a cluster?

eric

  • Hero Member
  • *****
  • Posts: 229
Re: limit number of workers, not just number of cpus
« Reply #2 on: August 20, 2008, 12:42:50 AM »
Restrictions are how you can limit a job to run on a particular cluster. Just put the cluster name in the "restrictions" field when you submit the job.

jesse

  • Sr. Member
  • ****
  • Posts: 40
Re: limit number of workers, not just number of cpus
« Reply #3 on: August 20, 2008, 03:03:17 AM »
Aha!
Since I am new to clusters I did not realize they could be used in the restrictions list as well. 
Thank you!