Job Execution on Eos
Print this article
Running jobs on Eos is similar Titan, except for some important differences:
- The compute nodes have 16 physical cores and no GPUs are present.
- Intel’s Hyper-threading (HT) technology, allows each physical core to appear as two logical cores so each node can functions as if it has 32 cores.
- The default option on Eos is to run with Hyper Threading. You need to use the
-j1option with the
apruncommand to explicitly disable HT.
- Each code should be tested to see how HT impacts its performance before HT is used.
Once resources have been allocated through the batch system, users can:
- Run commands in serial on the resource pool’s primary service node
- Run executables in parallel across compute nodes in the resource pool
The executable portion of a batch script is interpreted by the shell specified on the first line of the script. If a shell is not specified, the submitting user’s default shell will be used. This portion of the script may contain comments, shell commands, executable scripts, and compiled executables. These can be used in combination to, for example, navigate file systems, set up job execution, run executables, and even submit other batch jobs.
By default, commands in the job submission script will be executed on the job’s primary service node. The
aprun command is used to execute a binary on one or more compute nodes within a job’s allocated resource pool.
apruncommand within a batch job.