Andromeda is a shared resource, so it is important to be mindful of how your usage may impact other researchers.
- Don’t run any computational job on the login node; if they are used for computational jobs, it will adversely affect the entire cluster.
- Compute nodes are a shared resource; avoid arbitrarily using a large portion of the cluster whenever possible; not only will it adversely affect your fair-share priority for later jobs, but it will also make it difficult for other users to submit their workloads. Examples of arbitrarily excessive usage of resources include the following:
- Compute nodes allocated to a job sitting idle and not being used
- Using more cores and memory than required to complete the job within the time limit (requested cores and memory should be the minimum necessary for the job to complete within the time limit)
- Make a good-faith effort to make sure that the resources you request are necessary for the job you are running. For instance, if your job only runs on 4 cores, do not request a 64-core node for yourself, the other 60 cores will be blocked from doing useful work by others. This also applies to memory and GPU usage. Try to be as accurate as possible when specifying memory and cores for jobs.
- Temporary/Ephemeral data should be sent to /scratch. For example: when running Gaussian the temporary files are not needed after the job run and do not need snapshots taken.
- Sharing accounts/passwords is a violation of BC policy; All BC IT Policies apply to the cluster.
- The first time you login to the cluster, your password is temporarily set to your EagleID. Once you login, you will then be prompted to change it.
- The HPC cluster is to be used for research and other sanctioned activities only.
Recommended Job Limits (not enforced):
- 3600 cores per user
* Job limits do not apply to dedicated or reserved resources.