Difference between revisions of "BwUniCluster2.0/FAQ - broadwell partition"

From bwHPC Wiki
Jump to: navigation, search
(How to compile code on broadwell (= extension) nodes?)
(How to compile code on broadwell (extension) nodes?)
Line 19: Line 19:
 
icc/ifort -axCORE-AVX2
 
icc/ifort -axCORE-AVX2
 
</pre>
 
</pre>
On uc1e (= extension) login nodes:
+
On uc1e (extension) login nodes:
 
<pre>
 
<pre>
 
icc/ifort -xHost
 
icc/ifort -xHost

Revision as of 12:36, 14 September 2017

FAQs concerning best practice of bwUniCluster broadwell partition (aka "extension" partition).

1 Login

1.1 Are there separate login nodes for the bwUniCluster broadwell partition?

  • Yes, but primarily to be used for compiling code.

1.2 How to login to broadwell login nodes?

  • You can directly login on broadwell partition login nodes using
  $ username@uc1e.scc.kit.edu
  • If you login to the old uc1 login nodes, even though you can use broadwell nodes using the same procedure as 'compute nodes'.


2 Compilation

2.1 How to compile code on broadwell (extension) nodes?

On uc1 (old) login nodes:

icc/ifort -axCORE-AVX2

On uc1e (extension) login nodes:

icc/ifort -xHost

2.2 How to compile code working on the old and extension partition?

On uc1e (= extension) login nodes:

icc/ifort -xAVX -axCORE-AVX2

2.3 What happens with code compiled for old partition running on the extension partition?

Code will run but significantly slower since AVX2 will not be used. Please recompile your code accordingly.


3 Job execution

3.1 How to submit jobs to the broadwell (= extension) partition

The submitted job will be distributed either way to the broadwell nodes if specified correctly, i.e.:

msub -q multinode