Running jobs: Difference between revisions

Jump to navigation Jump to search
Added Narval to the tabbed section
(Update META link)
(Added Narval to the tabbed section)
Line 487: Line 487:
<tab name="Beluga">
<tab name="Beluga">
On Beluga, no jobs are permitted longer than 168 hours (7 days) and there is a limit of 1000 jobs, queued and running, per user. Production jobs should have a duration of at least an hour.  
On Beluga, no jobs are permitted longer than 168 hours (7 days) and there is a limit of 1000 jobs, queued and running, per user. Production jobs should have a duration of at least an hour.  
</tab>
<tab name="Graham">
On Graham, no jobs are permitted longer than 168 hours (7 days) and there is a limit of 1000 jobs, queued and running, per user. Production jobs should have a duration of at least an hour.
</tab>
</tab>
<tab name="Cedar">
<tab name="Cedar">
Line 515: Line 512:
''If you are unsure if your job requires a specific architecture, do not use this option.'' Jobs that do not specify a CPU architecture can be scheduled on either Broadwell or Skylake nodes, and will therefore generally start earlier.
''If you are unsure if your job requires a specific architecture, do not use this option.'' Jobs that do not specify a CPU architecture can be scheduled on either Broadwell or Skylake nodes, and will therefore generally start earlier.
</tab>
</tab>
<tab name="Graham">
On Graham, no jobs are permitted longer than 168 hours (7 days) and there is a limit of 1000 jobs, queued and running, per user. Production jobs should have a duration of at least an hour.
</tab>
<tab name="Narval">
On Narval, no jobs are permitted longer than 168 hours (7 days) and there is a limit of 1000 jobs, queued and running, per user. Production jobs should have a duration of at least an hour.
</tab>
<tab name="Niagara">
<tab name="Niagara">
<ul>
<ul>
cc_staff
782

edits

Navigation menu