Difference between revisions of "Rocky Kivlin"

From NIMBioS
(Created page with "= About = Kivlin Lab has purchased compute resources on the Rocky cluster. These resources are only available to accounts associated with the Kivlin Lab. Please specify you are associated with the Kivlin Lab when requesting an account. = Exclusive Nodes = {| class="wikitable" |- ! Node !! Type !! Architecture !! vCPU !! Memory !! Exclusivity |- | bull1 || compute || Xeon Gold 6430 (Sapphire Rapids) || 128 || 512G || 2/12/202...")
 
Line 3: Line 3:




= Exclusive Nodes =
= Kivlin Partition =
Below are the nodes in the Kivlin Partition:<br/>
 
{| class="wikitable"
{| class="wikitable"
|-
|-
! Node !! Type !! Architecture !! vCPU !! Memory !! Exclusivity
! Node !! Type !! Architecture !! vCPU !! Memory !! Exclusivity
|-
|-
| bull1 || compute || Xeon Gold 6430 (Sapphire Rapids) || 128 || 512G || 2/12/2024 - 2/12/2027
| bull1 || compute || Xeon Gold 6430 (Sapphire Rapids) || 128 || 512G || 2/13/2024 - 2/13/2027
|}
|}


Line 14: Line 16:
= Usage =
= Usage =


By default, accounts will use the <code>compute_all</code> partition which includes all shared pool resources.  When [[Rocky Job Anatomy|submitting a job to Rocky]], you will need to specify the <code>kivlin</code> partition.<br/><br/>
By default, accounts will use the <code>compute_all</code> partition which includes all shared pool resources.  When [[Rocky Job Anatomy|submitting a job to Rocky]], you will need to specify the <code>kivlin</code> partition as part of your batch file.<br/><br/>


Example batch file:<br/>
Example batch file:<br/>
Line 30: Line 32:
</pre>
</pre>


In the above batch file, you can see that we specify the <code>kivlin</code> partition followed by the <code>compute_all</code> partition.  With these parameters, the job schedule will look for available resources on the kivlin partition first.  If all those are in use it will then use resources from the shared pool.
In the above batch file, you can see that we specify the <code>kivlin</code> partition followed by the <code>compute_all</code> partition.  With these parameters, the job scheduler will look for available resources on the kivlin partition first.  If all those are in use it will then use resources from the shared pool.

Revision as of 21:59, 12 February 2024

About

Kivlin Lab has purchased compute resources on the Rocky cluster. These resources are only available to accounts associated with the Kivlin Lab. Please specify you are associated with the Kivlin Lab when requesting an account.


Kivlin Partition

Below are the nodes in the Kivlin Partition:

Node Type Architecture vCPU Memory Exclusivity
bull1 compute Xeon Gold 6430 (Sapphire Rapids) 128 512G 2/13/2024 - 2/13/2027


Usage

By default, accounts will use the compute_all partition which includes all shared pool resources. When submitting a job to Rocky, you will need to specify the kivlin partition as part of your batch file.

Example batch file:

#SBATCH --partition=kivlin,compute_all

#SBATCH --job-name=PYTHON_PRIME
#SBATCH --output=python_prime_%j.out
#SBATCH --mail-user=me@test.com
#SBATCH --mail-type=END

module load Python

python3 prime.py

In the above batch file, you can see that we specify the kivlin partition followed by the compute_all partition. With these parameters, the job scheduler will look for available resources on the kivlin partition first. If all those are in use it will then use resources from the shared pool.