Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
tools:psc [2026/05/19 16:29] – [Pittsburgh Super Computer] willtools:psc [2026/06/01 15:33] (current) – [Checking hour allocations] will
Line 9: Line 9:
   * Quick test for interactive queue: ''salloc''. See [[:tools:slurm]] for more   * Quick test for interactive queue: ''salloc''. See [[:tools:slurm]] for more
   * <wrap tip> use ''%%-p RM-shared --ntasks-per-node=1%%'' for lowest hour burn rate</wrap>   * <wrap tip> use ''%%-p RM-shared --ntasks-per-node=1%%'' for lowest hour burn rate</wrap>
-    * ''RM-shared'' memory limited to ''2GB*$ntasks_per_node'' (will see out-of-memory "oom" errors when exceeding)+    * ''RM-shared'' memory limited to ''2GB*$ntasks_per_node'' (will see out-of-memory "oom" errors when exceeding). See [[:tools:slurm]].
   * User Guide: https://www.psc.edu/resources/bridges-2/user-guide/   * User Guide: https://www.psc.edu/resources/bridges-2/user-guide/
   * For planned outages see: https://www.psc.edu/calendar/   * For planned outages see: https://www.psc.edu/calendar/
 +  * see [[:tools:usage_profiling]] for determining runtime and memory usage
    
 +Command line notes:
 <code=base> <code=base>
 ssh -Y $USER@bridges2.psc.edu # -Y for X11 display forwarding ssh -Y $USER@bridges2.psc.edu # -Y for X11 display forwarding
Line 60: Line 62:
 ===== Checking hour allocations ===== ===== Checking hour allocations =====
  
-To check the hours of specific job <code> sacct -j <job name>.batch --format=JobID,MaxRSS,AveRSS,TotalCPU </code>+To check the hours of specific job (also see [[:tools:usage_profiling]]) <code> sacct -j <job name>.batch --format=JobID,MaxRSS,AveRSS,TotalCPU </code>
  
 To check the hours in general: <code> projects </code> To check the hours in general: <code> projects </code>