Cedar/en: Difference between revisions

Updating to match new version of source page
(Updating to match new version of source page)
(Updating to match new version of source page)
Line 85: Line 85:


== Choosing a node type ==
== Choosing a node type ==
A number of nodes are reserved for jobs that require whole nodes. These are all 48-core nodes, i.e., '''there are no 32-core nodes set aside for whole node processing. If the job asks for 32 tasks per node, it will be moved into one of the bycore partitions and consequently (most likely) will end up running on a 48-core node'''.<br>
A number of 48-core nodes are reserved for jobs that require whole nodes. There are no 32-core nodes set aside for whole node processing. '''Jobs that request less than 48 cores per node can end up sharing nodes with other jobs.'''<br>
Most applications will run on either Broadwell or Skylake or Cascade Lake nodes, and performance differences are expected to be small compared to job waiting times. Therefore we recommend that you do not select a specific node type for your jobs. If it is necessary, use <code>--constraint=cascade</code>, <code>--constraint=skylake</code> or <code>--constraint=broadwell</code>.  If the requirement is for any AVX512 node, use <code>--constraint=[skylake|cascade]</code>.  See [[Running_jobs#Specifying_a_CPU_architecture|Specifying a CPU architecture]].
Most applications will run on either Broadwell or Skylake or Cascade Lake nodes, and performance differences are expected to be small compared to job waiting times. Therefore we recommend that you do not select a specific node type for your jobs. If it is necessary, use <code>--constraint=cascade</code>, <code>--constraint=skylake</code> or <code>--constraint=broadwell</code>.  If the requirement is for any AVX512 node, use <code>--constraint=[skylake|cascade]</code>.  See [[Running_jobs#Specifying_a_CPU_architecture|Specifying a CPU architecture]].


38,760

edits