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 [2011/04/07 05:24] svohr [Hardware] updated hardward specs |
||
---|---|---|---|
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| | ||
Line 85: | Line 86: | ||
#$ -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. | ||
+ | |||