This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
archive:computer_resources:campusrocks [2010/04/19 20:05] jstjohn |
archive:computer_resources:campusrocks [2015/04/13 18:55] ceisenhart |
||
---|---|---|---|
Line 13: | Line 13: | ||
^Machine ^GB RAM ^CPUs ^Cores ^MHz ^Model ^ | ^Machine ^GB RAM ^CPUs ^Cores ^MHz ^Model ^ | ||
- | |campusrocks.local(head node?)|30 |1 |1 |1000 |Dual-Core AMD Opteron(tm) Processor 2218 HE| | + | |campusrocks.local(head node?)|30 |4 |1 |2600 |Dual-Core AMD Opteron(tm) Processor 2218 HE| |
- | |campusrocks-0-2(through 30).local |15 |4 |2 |1800 |Dual-Core AMD Opteron(tm) Processor 2218 HE| | + | |campusrocks-0-2(through 30).local |15 |4 |2 |2664 | Intel(R) Xeon(R) CPU 5150 | |
+ | |campusrocks-0-(31,32).local |15 |8 |2 | 3192 | Intel(R) Xeon(TM) CPU| | ||
|campusrocks-1-0(through 31).local |15 |2 |1 |2592 |Dual-Core AMD Opteron(tm) Processor 2218 HE| | |campusrocks-1-0(through 31).local |15 |2 |1 |2592 |Dual-Core AMD Opteron(tm) Processor 2218 HE| | ||
+ | |campusrocks-2-(0,1).local |192 | 48| | | | | ||
campusrocks-0-6.local exceptionally has 30 GB RAM | campusrocks-0-6.local exceptionally has 30 GB RAM | ||
Line 66: | Line 68: | ||
They threaten to kill jobs found running on the head node. | They threaten to kill jobs found running on the head node. | ||
- | There is [[http://campusrocks.soe.ucsc.edu/roll-documentation/sge/5.2/|Online documentation]] of how to use sungrid to submit jobs on the cluster. The main commands are | + | There is [[http://www.rocksclusters.org/rocks-documentation/4.1/|online documentation]] of how to use sungrid to submit jobs on the cluster. The main commands are |
* qsub: Submits a job (create a shell script, then run "qsub -cwd shellscript") | * qsub: Submits a job (create a shell script, then run "qsub -cwd shellscript") | ||
* qdel: Delete a job | * qdel: Delete a job | ||
Line 85: | Line 87: | ||
#$ -V\\ | #$ -V\\ | ||
Your jobs use **your** environment variables. | Your jobs use **your** environment variables. | ||
+ | |||
+ | #$ -l mem_free=15g\\ | ||
+ | Your job goes to a node with at least 15g of free memory. There is probably something like '-l mem_avail' that works if you would like to schedule your job on a node with a certain amount of max memory available, even if some of it is currently in use. | ||
+ | |||