During prime time the following guidelines apply:
Interactive Nodes
- Interactive nodes should be used primarily for code development rather
than for production calculations.
- Time limits for jobs or scripts of jobs on the interactive nodes are
determined by the following schedule:
Number of Nodes Maximum Duration
--------------- -------------------------------------
1 to 20 0 hours*
21 to 544 0.5 hour
*This machine is intended for large jobs; hence the running of small jobs
on it is discouraged. Jobs using fewer than 21 nodes may be run for
brief periods provided they do not interfere with running larger jobs.
Jobs using fewer than 21 nodes may be terminated without warning and
without regard for the effects of such termination.
- Ganging jobs either manually or via scripts on the interactive nodes
violates the intent of these rules to provide equitable access to the
Paragon for both code development and production calculations for the user
community.
- A job or script of jobs that breaks these rules may be terminated without
notice and without regard to the effect of such termination.
Batch Nodes
- Batch nodes are accessed via a system of queues. The current queues and
their limits are given in the following table.
Queue Name Maximum Nodes Maximum Time
-------------- ------------- ------------
backgrnd.day 1024 1.25 hours
default.day 1024 1.25 hours
express.day 1024 1.25 hours*
sandia.day 1024 1.25 hours
develop.day 256 0.25 hour
*Requires management request and approval. The user requesting the use of
the express.day queue must have the request submitted via e-mail to
iparagon@cs.sandia.gov by his or her manager. The request must include
the project which requires the use of the express queue, must clearly
state why the normal queues are inadequate for the user's needs, and must
provide an estimate of how many jobs will be run, how many nodes each job
will use, and how long each job will run.
The develop.day queue is intended for code development. The other queues
may be used for code development or production calculations.
Users are permitted access to these queues based on their organizational
affiliation. Each user may have up to three jobs submitted per queue;
excess jobs will be deleted from the queues.