MeluXina
EESSI, the base of the EFP Federated Software Catalog,
is available system-wide on MeluXina via a SquashFS export of the software.eessi.io repository since early 2026.
Synchronisation
MeluXina is synchronised daily with the public EESSI infrastructure. This means that once new software has been integrated into EESSI, the maximum wait time for it to appear on the system is 24 hours.
Access
EESSI is only available on compute nodes, not on the login nodes. Other than this restriction the standard access instructions apply.
Usage
EESSI is available by default on the compute nodes but requires initialisation. See the initialisation instructions for the Federated Software Catalog and then continue with loading your required software.
Known problems and limitations
- Following system policy, EESSI is not available on login nodes. See also the MeluXina User Documentation.
System-specific best practices
Multi-node jobs
We provide an example of running a latency test between nodes from the OSU Micro-Benchmarks suite. This is done on 2 nodes, each with GPUs, and checking the device-to-device (node-to-node) latency:
# Allocate resources for the test (2 nodes, 1 task per node, 1 GPU per task)
salloc --time=00:30:00 --account="<SLURM_ACCOUNT>" --qos=default --gpus-per-task=1 --partition gpu --nodes 2 --ntasks-per-node 1
# Configure the EESSI environment and load the modules we need for our test
source /cvmfs/software.eessi.io/versions/2025.06/init/lmod/bash
module load OSU-Micro-Benchmarks/7.5-gompi-2024a-CUDA-12.6.0
# Check we have two different nodes
srun --mpi=pspmix -n 2 hostname
# Launch our latency test
srun --mpi=pspmix -n 2 osu_latency --accelerator cuda
The --mpi=pspmix is not strictly necessary, as it is in fact set by default in the environment via the
environment variable $SLURM_MPI_TYPE, we include it above for completeness.
Getting help with using FSC on MeluXina
If you need help with using EESSI on MeluXina, please contact EFP Helpdesk.