cc_staff
292
edits
Chapel: Difference between revisions
→Multi-locale Chapel
| Line 29: | Line 29: | ||
== Multi-locale Chapel == | == Multi-locale Chapel == | ||
Installing multi-locale (distributed-memory) Chapel requires fine-tuning its launcher for the specific physical interconnect on the cluster. Since Compute Canada clusters Cedar and Graham employ two different physical interconnects, we do not have one multi-locale Chapel module for both machines. Instead, multi-locale Chapel has been compiled in a separate directory as an experimental setup on each system: | Installing multi-locale (distributed-memory) Chapel requires fine-tuning its launcher for the specific physical interconnect on the cluster. Since Compute Canada clusters Cedar and Graham employ two different physical interconnects, we do not have one multi-locale Chapel module for both machines. Instead, multi-locale Chapel has been compiled in a separate directory as an experimental setup on each system. You can test this setup with the following Chapel code printing basic information about the nodes available inside your job: | ||
{{ | |||
File | |||
|name=probeLocales.chpl | |||
|lang="chapel" | |||
|contents= | |||
use Memory; | |||
for loc in Locales do | |||
on loc { | |||
writeln("locale #", here.id, "..."); | |||
writeln(" ...is named: ", here.name); | |||
writeln(" ...has ", here.numPUs(), " processor cores"); | |||
writeln(" ...has ", here.physicalMemory(unit=MemUnits.GB, retType=real), " GB of memory"); | |||
writeln(" ...has ", here.maxTaskPar, " maximum parallelism"); | |||
} | |||
}} | |||
module unload chapel-single | module unload chapel-single | ||