• Computing Survival Guide
• File Storage and Backup
• Hardware
• High Performance Computing
  • DSCR Support Information
  • High Performance Computing
  • Application Information
• OIT Training
• Printing with ePrint
• Public Computing Labs
• Software
• Tune Up Your Computer
• Virtualized Computing

• email this
• print
• download pdf
• bookmark this

Many users have asked about our policy of high- versus low-priority -- particularly, can you submit a job which just takes advantage of whatever machines/queues that are available? i.e. can I submit a job that uses both high- and low-priority resources?

The short answer is "No", you must indicate either high- or low-priority, not both, when you submit the job.

• If you submit the job as a high-priority job, then it will ONLY access your high-priority queues and it will not access any low-priority queues, even if low-priority queues are open and available
  • If your group has unusued high-priority queues, then your job will run immediately
  • If none of your high-priority queues are open, then your job will have to wait until sufficient resources are freed up within your high-priority group
• If you submit the job as a low-priority job, then it will access any low-priority queues that are available, including core resources as well as machines owned by other research groups
  • If your job is fairly large, there may not be enough free resources in the low-priority pool and so your job may have to wait
  • If your job is going to run for a long time, then your low-priority job can be slowed down if a high-priority job gets placed on the same machine(s) with it