Most
organizations have many SAS users performing a variety of query, reporting,
and modeling tasks and competing for the same resources. SAS Grid
Manager can help bring order to this environment by providing capabilities
such as the following:
-
specifying which jobs get priority
-
deciding the share of computing
resources used by each job
-
controlling the number of jobs
that are executing at any one time
In practice,
SAS Grid Manager submits work to the grid middleware, which acts as
a gatekeeper for the jobs submitted to servers. As jobs are submitted,
the middleware (such as Platform LSF) doles them out to grid nodes,
preventing any one machine from being overloaded. If more jobs are
submitted than can be run at once, the grid middleware submits as
many jobs as can be run. The middleware then holds the rest in a queue
until resources are free. The grid middleware can also use job priority
to determine whether a job is run immediately or held in a queue.
The application user notices
little or no difference when working with a grid. For example, users
can define a key sequence to submit a job to a grid rather than running
it on their local workstation. Batch jobs can be run using wrapper
code that adds the commands needed to run the job in the grid. SAS
Enterprise Guide applications can be set up to automatically insert
the code needed to submit the job to the grid.