BSCL: DQS configuration

The DQS configuration at BSCL

Workstations with Queues:

Machine Queue Name Complexes # of Queues Memory Limit CPU Time Limit

bi1.msi.umn.edu bi1 OCTANE
R10K
SGI 2 300 MB 48 Hours

bi2.msi.umn.edu bi2 OCTANE
R10K
SGI 2 300 MB 48 Hours

bi3.msi.umn.edu bi3 OCTANE
R10K
SGI 2 300 MB 48 Hours

bi4.msi.umn.edu bi4 OCTANE
R12K
SGI 2 300 MB 48 Hours

bi6.msi.umn.edu bi6 OCTANE
R12K
SGI 2 300 MB 48 Hours

bi7.msi.umn.edu bi7 OCTANE2
R12K
SGI 2 300 MB 48 Hours

bi9.msi.umn.edu bi9 OCTANE2
R12K
SGI 2 300 MB 48 Hours

bi10.msi.umn.edu bi10 OCTANE2
R12K
SGI 2 300 MB 48 Hours

bi11.msi.umn.edu bi11 OCTANE2
R12K
SGI 2 300 MB 48 Hours

Machine	Queue Name	Complexes	# of Queues	Memory Limit	CPU Time Limit
bi1.msi.umn.edu	bi1	OCTANE R10K SGI	2	300 MB	48 Hours
bi2.msi.umn.edu	bi2	OCTANE R10K SGI	2	300 MB	48 Hours
bi3.msi.umn.edu	bi3	OCTANE R10K SGI	2	300 MB	48 Hours
bi4.msi.umn.edu	bi4	OCTANE R12K SGI	2	300 MB	48 Hours
bi6.msi.umn.edu	bi6	OCTANE R12K SGI	2	300 MB	48 Hours
bi7.msi.umn.edu	bi7	OCTANE2 R12K SGI	2	300 MB	48 Hours
bi9.msi.umn.edu	bi9	OCTANE2 R12K SGI	2	300 MB	48 Hours
bi10.msi.umn.edu	bi10	OCTANE2 R12K SGI	2	300 MB	48 Hours
bi11.msi.umn.edu	bi11	OCTANE2 R12K SGI	2	300 MB	48 Hours

Queue Complexes:

Queue complexes allow users to select queues based on specific resources. Currently, we have 4 complexes: R10K, R12K, OCTANE2 and SGI.

R10K includes all the workstations with R10000 processors (bi1, bi2, bi3).
R12K includes all workstations with R12000 processors (bi3, bi4, bi6, bi7, bi9, bi10, bi11).
OCTANE2 includes all the SGI OCTANE2 workstations (bi7, bi9, bi10, bi11).
SGI includes all SGI hosts.
Currently this is the default if no resource list is requested.

To use the queue complexes, you must use the #$ -l (complexname) directive in your DQS script. For example:

#$ -S /bin/csh #$ -l (SGI) #$ -cwd ./a.out

will run the a.out program on any available SGI.

Queue Limits:

If the maximum cpu time is exceeded, the system will send a SIGXCPU to your process. If you choose to trap and ignore the signal, the operating system will kill your process.

Attempts to exceed memory limits will simply result in denial of memory allocation to whichever system call requests it. Your process will not be explicitly killed, but it may die, depending on how you've written your code.

Submitting and monitoring jobs

This information is available in alternative formats upon request by individuals with disabilities. Please send email to alt-format@msi.umn.edu or call 612-624-0528.

HOME | QUESTIONS | FEEDBACK
Events | Links | People | Publications | Support | Welcome

URL: http://www.msi.umn.edu /sdml/info/dqs/config.html

This page last modified on Wednesday, 23-Apr-2008 11:14:47 CDT

Please direct questions or problems to help@msi.umn.edu

Website related questions or problems should be directed to webmaster@msi.umn.edu
The Supercomputing Institute does not collect personal information on visitors to our website. For the University of Minnesota policy, see www.privacy.umn.edu.