|Table of Contents|
High Level Differences from ikt.hyak, the 1st generation Hyak system (retired March 2020).
- Mox is an entirely separate cluster. They share nothing with one another.
- You only get what you ask for, regardless of the resources available on the node. If you ask for 1 CPU, you'll only get one. If you ask for 1GB of RAM, you'll only get 1GB.
- An allocation won't get the same set of nodes all the time, just access to the particular number of nodes to which they're entitled.
- No occasional preemption in ckpt (formerly bf queue) for the moment.
- Preempted jobs get 10s to do something smart before being killed and requeued.
- Please report any problems to firstname.lastname@example.org with Hyak as the first word in the subject. Please also let us know you're using mox not ikt.
BBCP = mox1.hyak.uw.edu or mox2.hyak.uw.edu
Internal to Hyak systems
You can copy files at high speed without a password between the Hyak systems using commands like the ones below.
cat /gscratch/<my short group>/usage_report.txt
Jobs in Allocation
Build Allocation - usage limited by core count and time
srun -p build --mem=100G --time=2:00:00 --pty bash -l
srun -p <my short group name> -A
<my short group name> --mem=100G --time=2:00:00 --pty bash -l
Show Allocation Information
## Job Name
## Allocation Definition
## Tasks per node (Slurm assumes you want to run 28 tasks, remove 2x # and adjust parameter if needed)
## Walltime (ten minutestwo hours)
# E-mail Notification, see man sbatch for options
##turn on e-mail notification
## Memory per node
#SBATCH --mem=2G 100G
## Specify the working directory for this job
module load icc_<version>-impi_<VERSION>
See articles on mox at below link (scroll down to links with prefix mox):
You can find additional documentation that applies to both mox and ikt on the main Hyak User Wiki.