The Department of Computer Science have purchased 8 nodes in ShARC that each have much more than the standard amount of RAM per node.
2x Intel Xeon E5-2630 v3 processors (2.40 GHz, 8 cores per socket i.e. 16 total)
768 GB RAM (48 GB / CPU core)
2x Intel Xeon Gold 6138 processors (2.00GHz, 20 cores per socket i.e. 40 total)
768 GB RAM (19.2 GB / CPU core)
Access to the node is managed by the RSE team. Access policy:
PhD students, researchers and staff in Computer Science can all request access to the nodes.
Access to others who are collaborating on projects with some Computer Science / RSE involvement can be made on a case-by-case basis.
Access to Computer Science MSc students can be made on a case-by-case basis.
A number of other users were granted access before this policy was developed.
To request access complete this Google Form and someone within the RSE team will then respond with further information.
To use the nodes you must:
Be made a member of the
rse Grid Engine (scheduler) Access Control List (ACL i.e. user group);
Submit jobs using the
rse Grid Engine Project;
Start interactive jobs in
rse-interactive.q Grid Engine Cluster Queue;
Start batch jobs in the
rse.q Grid Engine Cluster Queue;
Once you have obtained permission to use the nodes you can request an interactive session on one of the nodes using:
qrshx -P rse -q rse-interactive.q
-P rse specifies that you want to use the
rse project for your session,
which gives you access to these big memory nodes and
ensures that your interactive session can run in the
rse-interactive.q job queue
(as can be seen if you subsequently run
qstat -u $USER from within your session).
rse-interactive.q job queue has a maximum job runtime (
h_rt) of four hours,
as is standard for interactive jobs on SHARC.
Jobs can be submitted to the nodes by adding the
-P rse and
-q rse.q parameters.
For example, create a job script named
my_job_script.sh with the contents:
#!/bin/bash #$ -P rse #$ -q rse.q echo "Hello world"
You can of course add more options to the script such as a request for additional RAM (e.g.
$# -l rmem=10G).
Run your script with the
You can use the
qstat command to check the status of your current job.
An output file is created in your home directory that captures your script’s outputs.
See Starting interactive jobs and submitting batch jobs for more information on job submission and the Sun Grid Engine scheduler.