Difference between revisions of "HPC-Dictionary"
| Line 13: | Line 13: | ||
== Node == | == Node == | ||
| − | + | A node is an individual computer consisting of one or more sockets. | |
=== Backend Node === | === Backend Node === | ||
| Line 31: | Line 31: | ||
Login nodes are reserved for connecting to the cluster of a facility. Most of the time they can also be used for testing and performing interactive tasks (e.g. the analysis of previously collected application profiles). These test runs should generally not exceed execution times of just a few minutes and may only be used to verify that your software is running correctly on the system and its environment before submitting batch jobs to the batch system. | Login nodes are reserved for connecting to the cluster of a facility. Most of the time they can also be used for testing and performing interactive tasks (e.g. the analysis of previously collected application profiles). These test runs should generally not exceed execution times of just a few minutes and may only be used to verify that your software is running correctly on the system and its environment before submitting batch jobs to the batch system. | ||
| − | == CPU == | + | == Central Processing Unit (CPU) == |
TODO | TODO | ||
| Line 37: | Line 37: | ||
== Socket == | == Socket == | ||
| − | + | A socket consists of one or more cores sharing the same memory. | |
== Cluster == | == Cluster == | ||
| − | + | A cluster referes to a collection of multiple nodes, which are connected via a network offering high bandwidth with low lateny communication. Accessing a cluster is possible by connecting to its specific login nodes. | |
== Random Access Memory (RAM) == | == Random Access Memory (RAM) == | ||
Revision as of 13:54, 17 April 2018
Unix
TODO
Unix File System
TODO
Environment Variables
TODO
Node
A node is an individual computer consisting of one or more sockets.
Backend Node
Backend nodes are reserved for executing memory demanding and long running applications. They are the most powerful, but also most power consuming part of a cluster as they make up around 98% of it. Since these nodes are not directly accessable by the user, a scheduler manages their access. In order to run on these nodes, a batch job needs to be submitted to the batch system via a scheduler specific command.
Copy Node
Copy nodes are reserved for transfering data to or from a cluster. They usually offer a better connection than other nodes and minimize the disturbance of other users on the system. Depending on the facility, software installed on these nodes may differ from other ones due to their restricted use case, though not every facility chooses to install a designated copy node at all. As an alternative login node may be used to move data between systems.
Frontend Node
Synonym for login node.
Login Node
Login nodes are reserved for connecting to the cluster of a facility. Most of the time they can also be used for testing and performing interactive tasks (e.g. the analysis of previously collected application profiles). These test runs should generally not exceed execution times of just a few minutes and may only be used to verify that your software is running correctly on the system and its environment before submitting batch jobs to the batch system.
Central Processing Unit (CPU)
TODO
Socket
A socket consists of one or more cores sharing the same memory.
Cluster
A cluster referes to a collection of multiple nodes, which are connected via a network offering high bandwidth with low lateny communication. Accessing a cluster is possible by connecting to its specific login nodes.
Random Access Memory (RAM)
TODO
Scalability
TODO