General Documentation
- Welcome FAQ
- Secure Shell SSH
- Available Software
- Installing Software
- Guidelines and Policies
- Glossary
- Grant Support
- Sharing Data
- Containers & Singularity
- UserGroup Presentations
- Jupyter Notebook Usage
LSF Primer
Lilac Cluster Guide
Juno Cluster Guide
Cloud Resources
Backup Policy on server/node local drives
File lists
Page History
The new juno cluster is now available only for testing. Please request "Access another cluster" from http://hpc.mskcc.org/compute-accounts/account-change-request/ if you want to participate in the test. juno currently has 216 CPUs. The login node is juno, a running CentOS 7. Nodes jx01-jx10 are running CentOS 7, and node ju14 is running CentOS 6. All juno nodes have access to the solisi Isilon file systems. CentOS 7 nodes also have access to /juno GPFS storage.
Differences in LSF Configuration between
...
juno and
...
luna
- We reserve ~12GB of RAM per host for the operating system and GPFS on Juno CentOS 7 hosts.
- On each jx## node (CentOS 7, GPFS installed), 240GB of RAM is available for LSF jobs.
- On each ju## node (CentOS 6, no GPFS), 250GB of RAM is available for LSF jobs.
- When specifying RAM for LSF jobs, specify GB of RAM per slot/task on Juno, or per job on luna.
- All jobs must have -W (maximum execution Walltime) specified on juno. Please do not use -We on juno.
- There is no /swap on CentOS 7 nodes. Memory usage is enforced by cgroups so jobs never swap. A job will be terminated if memory usage exceeds its LSF specification.
- To check jobs which are DONE or status EXIT, use "bhist -l JobID" or "bhist -n 0 -l JobID". bacct is also available. "bjobs -l JobID" only shows RUNNING and PEND jobs.
- There is no iounits resource on juno.
...