Skip to main content

Latest Tweets

  • New post: High-performance computing for Economists 2017 edition https://t.co/eoEHjGg8X9
    about 1 month ago via VirtualRDC
  • New post: ANNOUNCEMENT: EMERGENCY DOWNTIME on ecco cluster July 21-22 2017 https://t.co/QgpTGjM2Xj
    about 1 month ago via VirtualRDC
  • Page edited: World Statistical Congress 2015 (ISI2015) session on "Synthetic establishment microdata around the https://t.co/wqHFOXha3x
    about 3 months ago via VirtualRDC

SDSx Queues

Print Friendly, PDF & Email

The following job submission queues are configured on SDSx as of 2014-06-22:

Queue name Processor * hours limit Wallclock limit Memory
per job limit
Max cores
per job limit
Jobs
per user limit
Notes
interactive n.a. 2 hours 4GB n.a. 1 All menu entries for software run as jobs
on the interactive queue.
regular* [default] n.a. none
(defaults to 4hrs)
256GB  8 2
sas n.a. none none none none Used for SAS jobs, redirects jobs to the node with SAS installed
 HPC  none  none  none  none  none Jobs can be submitted by anybody to the HPC
queue, but no jobs are run without explicit approval
by the system owner.
 harvest  n.a.  1  --  --  -- Harvest jobs are hard-limited to 1 hour, but any number can
be submitted.

By default, all non-interactive jobs have a wallclock limit of as noted above - if you need to submit longer jobs, you will need to write a qsub script (at present our q-utilities do not support increasing wallclock limits), see page on Advanced qsub.

By default, all interactive jobs that are submitted through the NX interface are scheduled through the interactive queue, and all other jobs, submitted through the q-utilities or through a command-line qsub submission are submitted to the  regular queue. In order to submit to any of the other queues, assuming you have access rights, you need to specify

-q (queue name)

on the qsub command line, e.g.

qsub -q harvest myjob.qsub

or embed it into the qsub script as

#PBS -q (queue name)