4.1.1. Breniac infrastructure#
Breniac login infrastructure#
Breniac was the VSC’s Tier-1 cluster hosted by KU Leuven, and it was decomissioned in December 2022. This page is obsolete, and we keep it only for the future reference.
Direct login using SSH is possible to all login infrastructure.
Note
Only users involced in an active Tier-1 project have access to the infrastructure.
Two types of login nodes are available:
a classic login node, i.e., SSH access.
login1-tier1.hpc.kuleuven.belogin2-tier1.hpc.kuleuven.be
a login node that provides a desktop environment that can be used for, e.g., visualization. The NX login node will start a session on a login node that has a GPU, i.e.,
login2-tier1.hpc.kuleuven.be.
Hardware details#
408 skylake nodes
2 Xeon Gold 6132 CPU@2.6GHz, 14 cores each
192 GB RAM (memory bandwith and latency measurements)
75 GB SSD local disk
436 broadwell nodes
2 Xeon E5-2680v4 CPUs@2.4GHz, 14 cores each
128 GB RAM (memory bandwith and latency measurements)
75 GB SSD local disk
144 broadwell nodes
2 Xeon E5-2680v4 CPUs@2.4GHz, 14 cores each
256 GB RAM
75 GB SSD local disk
The nodes were connected using an Infiniband EDR network.
Breniac storage#
Your $VSC_HOME and $VSC_DATA directory are mounted on the Breniac
login and compute nodes. See your VSC institute’s information on local
storage about policies and quota.
Note
$VSC_HOME and $VSC_DATA are mounted using NFS, so they can not
be used for parallel I/O. If your software benefits from using a
parallel file system, please use $VSC_SCRATCH.
Variable |
Type |
Access |
Backup |
Default quota |
|---|---|---|---|---|
$VSC_SCRATCH $VSC_SCRATCH_SITE |
GPFS |
breniac |
NO |
1 TB |
$VSC_SCRATCH_NODE |
ext4 |
breniac, job only |
NO |
75 GB |
The path names given below should be adapted to reflect your home institution and VSC account number.
Variable |
Name |
|---|---|
$VSC_HOME |
/user/leuven/30X/vsc30XYZ |
$VSC_DATA |
/data/leuven/30X/vsc30XYZ |
$VSC_SCRATCH $VSC_SCRATCH_SITE |
/scratch/leuven/30X/vsc30XYZ |
$VSC_SCRATCH_NODE |
/local_scratch |