Please note: The FAQ pages at the HPCVL website are continuously being revised. Some pages might pertain to an older configuration of the system. Please let us know if you encounter problems or inaccuracies, and we will correct the entries.
Grid Engine uses the notion of a queue to distinguish between the different different types of jobs and the different components of the HPCVL cluster. Grid Engine queues can allow execution of many jobs concurrently, and Grid Engine tries to start new jobs in the queue that is most suitable and least loaded.
Note, that a job is always associated with its queue, and depends on the status of this queue, but, users do not need to submit jobs directly to a queue. You only need to specify the requirement profile of the job, which includes memory, available software and type of job (parallel or not, MPI,...).
Although you don't submit jobs directly to a queue you still need to know which queue is handling your job and what are the characteristics of this queue. On the HPCVL system, we have presently five different queues that are used for different purposes. If you type
you will see a list of all available queues. In particular, you'll find the following:
production.q This is the default queue. All jobs other than simple short test jobs are sent to this queue automatically. It is associated with the M9000 Cluster of Fujitsu Sparc64-VII based Sun Enterprise M9000 servers. It is used to schedule serial and parallel jobs to these high-memory dually-threaded nodes m9k00[1-8].
vf.q This queue is associated with the Victoria Falls Cluster of Niagara-2 based Sun T5140 servers. It is used to schedule serial and parallel jobs to these highly multi-threaded nodes v[01-73].
abaqus.q This queue is used to schedule software that does not run on the Solaris/Sparc platform and requires a Linux x86 based server instead. Such software includes Fluent, Abaqus, and new versions of Matlab. The queue schedules serial and parallel jobs to nodes sw00[11-51].