Nathan Albin
Wildcat
Head Node
Compute Nodes
Job Scheduler
| Feature | Interactive Jobs | Non-Interactive Jobs (Batch) |
|---|---|---|
| Interaction | Direct, real-time interaction | No direct interaction during run |
| Input | Typed commands, direct manipulation | Pre-defined in a script |
| Output | Displayed on screen in real-time | Written to files |
| Duration | Typically shorter | Can be short or very long |
| Use Cases | Testing, debugging, exploration | Large computations, automation |
| User Presence | Requires active user connection | Can run without active connection |
| Use Case | Description |
|---|---|
| Standard Single-Core Computing on a Powerful Server | Tasks that might be too slow or memory-intensive on a personal computer |
| Multi-threaded Computing on a Multi-Core Server | Computations that can be broken down into parallel tasks on a single powerful node |
| GPU Computing | Tasks that can use specialized processors that significantly accelerate certain types of computations, particularly those involving large amounts of parallel data processing |
| Multi-Node Processing using MPI | Very large-scale problems that require the combined power of multiple nodes |
You have a few options
Options
sbatch <scriptname> to start a jobkstat --me to check on a jobkstat -d 1 info on jobs ran in past day
Output written to slurm-xxxxxxxxx.out