blog
June 2010
May 2010
April 2010
March 2010
February 2010
December 2009
November 2009
October 2009
August 2009
July 2009
June 2009
May 2009
Need to adapt the number of resources made available to users based on workload?
Use the dynamic and Scheduler state-aware node sources:
“Scheduler loading” policy – acquires/releases nodes according to the scheduler load, which can be characterized for example by the number of nodes per task.
For example, if the policy is configured to “1 node per task” and if a job with 10 tasks is submitted, then 10 nodes will be dynamically acquired from the infrastructure.
This policy allows to configure the number of resources which will be always enough for the scheduler. Nodes are acquired and released according to scheduler loading factor which is a number of tasks per node. This policy requires scheduler URL, user name and password. It is important to correctly configure maximum and minimum nodes that this policy will try to hold.
Maximum number should not be greater than potential nodes number which is possible to deploy to underlying infrastructure.
If there are more currently acquired nodes than necessary, policy will release them one by one after having waited for a “release period” delay. This smooth release procedure is implemented because deployment time is greater than release one. Thus, this waiting time deters policy from spending all its time trying to deploy nodes.
No Comments »
No comments yet.
RSS feed for comments on this post. TrackBack URL