Hyperion system¶

How to connect to Hyperion¶

Prerequisites¶

Before connecting to Hyperion, ensure you have:

1. An active account on Hyperion.
2. An SSH client installed on your local machine. UNIX-based systems, including macOS and Linux, typically come pre-installed with an SSH client. For Windows users, software like PuTTY or MobaXTerm are some recommended options.

SSH Login¶

To establish a connection to Hyperion, use the following command:

$ ssh <username>@hyperion.sw.ehu.es

Replace <username> with your actual Hyperion username.

You can also establish direct connection with the login nodes:

$ ssh username@hyperion-01.sw.ehu.es
$ ssh username@hyperion-02.sw.ehu.es

Upon successful connection, users will be greeted with a shell on one of Hyperion's login nodes. Here, you can manage your files, compile code, or prepare batch submission scripts.

Security Recommendations¶

1. Public Key Authentication: While password-based logins are simple, using SSH key pairs for authentication is much more secure. Implementing public key authentication enhances security by making unauthorized access significantly more challenging.

2. Monitor Activity: Regularly review the list of active sessions and last logins to your Hyperion account. If you detect any unfamiliar activity, report it to our support team immediately.

Specifications¶

The cluster currently integrates nodes with two distinct Intel Xeon microarchitectures: Icelake and Cascadelake. When compiling software, it's imperative to consider the specific microarchitecture to optimize performance.

For interconnection, Hyperion employs Infiniband HDR technology. This provides a bandwidth of up to 200 Gb/s per direction and ensures low latency in data communication between nodes.

Filesystems and IO¶

Login Nodes¶

• Hyperion has 2 login nodes: hyperion-01.sw.ehu.es and hyperion-02.sw.ehu.es.
• Each node has two sockets populated with a 48 core Intel Xeon Platinum 8362 each.
• Each node has 256 GB of RAM.

Cluster Architecture Considerations¶

Hyperion is a heterogeneous cluster, composed of nodes with various microarchitectures including Cascadelake, Icelake and Emerald Rapids nodes.

Compiling Your Code¶

When compiling your code, it's essential to target the specific microarchitecture of the node you intend to run on. For reliable results and performance, compile and execute programs on nodes of the same microarchitecture. For instance, if you're compiling your code for a Cascadelake node, you should also run it on a Cascadelake node. Using binaries compiled for one microarchitecture on a different microarchitecture may lead to unpredictable behaviors, performance issues, or even application crashes.

Software¶

Compiling your code¶

Intel compilers are recommended for building your applications on Hyperion. There is no system default modulefile that takes care of this. Use the module avail command to see what versions are available and load an Intel compiler module before compiling. For example:

$ module load intel/2022a

Notice that when a compiler module is loaded, some environment variables are set or modified to add the paths to certain commands, include files, or libraries, to your environment. This helps to simplify the way you do your work.

As an alternative, Hyperion also offers a collection of open source tools such as compilers or scientific libraries. Use module avail command to see versions available. For example:

module avail intel 
module avail FFTW

To learn more about compilers and scientific libraries checkout Environment Modules and the Compilers sections.