General/What is Viper - Revision history

Pysdlb at 15:34, 8 November 2022

2022-11-08T15:34:16Z

Pysdlb at 16:57, 7 November 2022

2022-11-07T16:57:56Z

Pysdlb at 13:52, 13 October 2022

2022-10-13T13:52:30Z

Pysdlb at 14:39, 18 July 2022

2022-07-18T14:39:52Z

Pysdlb at 09:38, 3 May 2022

2022-05-03T09:38:22Z

Pysdlb at 13:48, 17 June 2019

2019-06-17T13:48:08Z

Pysdlb at 10:51, 17 June 2019

2019-06-17T10:51:52Z

Pysdlb at 10:50, 17 June 2019

2019-06-17T10:50:46Z

Pysdlb at 10:49, 17 June 2019

2019-06-17T10:49:00Z

Pysdlb at 10:21, 13 June 2019

2019-06-13T10:21:36Z

@@ Line 55: / Line 55: @@
 == Queues available ==
-There are as previously mentioned 3 main queues that jobs to be sent to:
+There are as previously mentioned 3 main queues that jobs are to be sent to:
 * compute - this queue will submit jobs to the 180 compute nodes
@@ Line 71: / Line 71: @@
 * 180 compute nodes, each with 2x 14-core Intel Broadwell E5-2680v4 processors (2.4 –3.3 GHz), 128 GB DDR4 RAM
 * 4 High memory nodes, each with 4x 10-core Intel Haswell E5-4620v3 processors (2.0 GHz), 1TB DDR4 RAM
-* 4 GPU nodes, each identical to compute nodes with the addition of a Nvidia Ampere A40 GPU per node
+* 4 GPU nodes, each identical to compute nodes with the addition of an Nvidia Ampere A40 GPU per node
 * 2 Visualisations nodes with 2x Nvidia GTX 980TI
 * Intel [http://www.intel.com/content/www/us/en/high-performance-computing-fabrics/omni-path-architecture-fabric-overview.html Omni-Path] interconnect (100 Gb/s node-switch and switch-switch)
 * 500 TB parallel file system ([http://www.beegfs.com/ BeeGFS])
-The compute nodes ('''compute''' and highmem ) are '''stateless''', with the GPU and visualisation node are stateful.
+The compute nodes ('''compute''' and highmem ) are '''stateless''', with the GPU and visualisation nodes being stateful.
 * Note: the compute nodes that have no persistent operating system storage between boots (e.g. originates from hard drives being the persistent storage mechanism). Stateless nodes do not necessarily imply diskless, as ours have 128Gb SSD temporary space too.
@@ Line 105: / Line 105: @@
 | [[File:Node-visualisation.jpg]]
 | '''4'''
-| These are specialised accelerator nodes with a Nvidia A40 per node and 128 GB of RAM
+| These are specialised accelerator nodes with an Nvidia A40 per node and 128 GB of RAM
 |-
 | [[File:Node-visualisation.jpg]]
@@ Line 118: / Line 118: @@
-== Further Information ==
+==Next Steps==
 * [[general/Batch|Batch Jobs]]

@@ Line 71: / Line 71: @@
 * 180 compute nodes, each with 2x 14-core Intel Broadwell E5-2680v4 processors (2.4 –3.3 GHz), 128 GB DDR4 RAM
 * 4 High memory nodes, each with 4x 10-core Intel Haswell E5-4620v3 processors (2.0 GHz), 1TB DDR4 RAM
-* 4 GPU nodes, each identical to compute nodes with the addition of 4x Nvidia Tesla K40m GPUs per node
+* 4 GPU nodes, each identical to compute nodes with the addition of a Nvidia Ampere A40 GPU per node
 * 2 Visualisations nodes with 2x Nvidia GTX 980TI
 * Intel [http://www.intel.com/content/www/us/en/high-performance-computing-fabrics/omni-path-architecture-fabric-overview.html Omni-Path] interconnect (100 Gb/s node-switch and switch-switch)
 * 500 TB parallel file system ([http://www.beegfs.com/ BeeGFS])
-The compute nodes ('''compute''' and highmem ) are '''stateless''', with the GPU and visualisation node are statefull.
+The compute nodes ('''compute''' and highmem ) are '''stateless''', with the GPU and visualisation node are stateful.
 * Note: the compute nodes that have no persistent operating system storage between boots (e.g. originates from hard drives being the persistent storage mechanism). Stateless nodes do not necessarily imply diskless, as ours have 128Gb SSD temporary space too.
@@ Line 105: / Line 105: @@
 | [[File:Node-visualisation.jpg]]
 | '''4'''
-| These are specialised accelerator nodes with 4 Nvidia K40 per node and 128 GB of RAM
+| These are specialised accelerator nodes with a Nvidia A40 per node and 128 GB of RAM
 |-
 | [[File:Node-visualisation.jpg]]

@@ Line 5: / Line 5: @@
 A supercomputer is a computer with a high level of computing performance compared to a general-purpose computer. It achieves this level of performance by allowing the user to split a large job into smaller computation tasks which then run in parallel, or by running a single task with many different scenarios on the data across parallel processing units.
-The point of having a high-performance computer is so that the individual nodes can work together to solve a problem larger than any one computer can easily solve. And, just like people, the nodes need to be able to talk to one another in order to work meaningfully together. Of course, computers talk to each other over networks, and there is a variety of computer network (or interconnect) options available for the business clusters (see here for an overview of cluster interconnects).
+The point of having a high-performance computer is so that the individual nodes can work together to solve a problem larger than any one computer can easily solve. And, just like people, the nodes need to be able to talk to one another in order to work meaningfully together. Of course, computers talk to each other over networks, and there is a variety of computer network (or interconnect) options available for business clusters (see here for an overview of cluster interconnects).
 Supercomputers generally aim for the maximum in capability computing rather than capacity computing. Capability computing is typically thought of as using the maximum computing power to solve a single large problem in the shortest amount of time. Often a capability system is able to solve a problem of a size or complexity that no other computer can, e.g., ''a very complex weather simulation application''.
@@ Line 51: / Line 51: @@
 === Interactive Sessions ===
-This is a slightly different way of using Viper and uses the power of the compute cluster with a user interactive session. For more information see [[General/Interactive|interactive session]].
+This is a slightly different way of using Viper and uses the power of the compute cluster with a user-interactive session. For more information see [[General/Interactive|interactive session]].
 == Queues available ==
@@ Line 68: / Line 68: @@
 === Physical Hardware ===
-Viper is based around the Linux operating system and is composed of approximately 5,500 processing cores with the following specialised areas:
+Viper is based on the Linux operating system and is composed of approximately 5,500 processing cores with the following specialised areas:
 * 180 compute nodes, each with 2x 14-core Intel Broadwell E5-2680v4 processors (2.4 –3.3 GHz), 128 GB DDR4 RAM
 * 4 High memory nodes, each with 4x 10-core Intel Haswell E5-4620v3 processors (2.0 GHz), 1TB DDR4 RAM
@@ Line 109: / Line 109: @@
 | [[File:Node-visualisation.jpg]]
 | '''1'''
-| This is a specialised accelerator node with a 2 Nvidia P100 per node and 128 GB of RAM
+| This is a specialised accelerator node with 2 Nvidia P100 per node and 128 GB of RAM
 |-
 | [[File:Node-visualisation.jpg]]

@@ Line 9: / Line 9: @@
 Supercomputers generally aim for the maximum in capability computing rather than capacity computing. Capability computing is typically thought of as using the maximum computing power to solve a single large problem in the shortest amount of time. Often a capability system is able to solve a problem of a size or complexity that no other computer can, e.g., ''a very complex weather simulation application''.
-A high-performance computer like Viper has a lot of elements of a desktop computer — processors, memory, disk, operating system — just more of them. High-performance computers split off some of the tasks into separate elements to gain performance. An example of this on Viper is how it handles disk storage, which is a separate server with all of the storage directly connected to it. This is then connected across a very fast network to all of the other individual computers (referred to as nodes).
+A high-performance computer like Viper has a lot of elements of a desktop computer — processors, memory, disk, operating system — just more of them. High-performance computers split off some of the tasks into separate elements to gain performance. An example of this on Viper is how it handles disk storage, which is a separate server with all of the storage directly connected to it. This is then connected across a high-speed network to all other individual computers (referred to as nodes).
 Viper's real compute power is achieved by having a large amount of standard compute nodes ('''Compute'''), in our case 180 of them. Each of those nodes has 28 processing cores, so a total of 5040 processing cores ( i.e. 180 x 28 cores ). Some specialised nodes are included which are more suited to dedicated applications, such as high memory ('''Highmem''') nodes and GPU accelerator ('''GPU''') nodes which are particularly suited to large memory modelling and machine learning respectively.
@@ Line 35: / Line 35: @@
 == Using Viper ==
-As a user when you log in to Viper you will log into one of the two login nodes which will provide a Linux style command-line interface. From here it is possible to load modules (i.e. software), download data, compile code and submit jobs to the cluster. Note that the login node is not the computing cluster, this is accessed by submitting a job to the scheduler (SLURM).
+As a user when you log in to Viper you will log into one of the two login nodes which will provide a Linux-style command-line interface. From here it is possible to load modules (i.e. software), download data, compile code and submit jobs to the cluster. Note that the login node is not the computing cluster, this is accessed by submitting a job to the scheduler (SLURM).
 === Module Add ===
@@ Line 61: / Line 61: @@
 * GPU - this queue will submit jobs to the GPU accelerator nodes
-These queues are managed by Viper's job scheduler, for more information about [[general/Slurm|SLURM]].
+Viper's job scheduler manages these queues, for more information about [[general/Slurm|SLURM]].
 == Viper Specifications ==

@@ Line 1: / Line 1: @@
 == Introduction ==
-Viper is the University of Hull's supercomputer and is located on site with its own dedicated team to administrate it and develop applications upon it.
+Viper is the University of Hull's supercomputer and is located on-site with its own dedicated team to administrate it and develop applications upon it.
 A supercomputer is a computer with a high level of computing performance compared to a general-purpose computer. It achieves this level of performance by allowing the user to split a large job into smaller computation tasks which then run in parallel, or by running a single task with many different scenarios on the data across parallel processing units.
-The point of having a high performance computer is so that the individual nodes can work together to solve a problem larger than any one computer can easily solve. And, just like people, the nodes need to be able to talk to one another in order to work meaningfully together. Of course computers talk to each other over networks, and there are a variety of computer network (or interconnect) options available for business cluster (see here for an overview of cluster interconnects).
+The point of having a high-performance computer is so that the individual nodes can work together to solve a problem larger than any one computer can easily solve. And, just like people, the nodes need to be able to talk to one another in order to work meaningfully together. Of course, computers talk to each other over networks, and there is a variety of computer network (or interconnect) options available for the business clusters (see here for an overview of cluster interconnects).
 Supercomputers generally aim for the maximum in capability computing rather than capacity computing. Capability computing is typically thought of as using the maximum computing power to solve a single large problem in the shortest amount of time. Often a capability system is able to solve a problem of a size or complexity that no other computer can, e.g., ''a very complex weather simulation application''.
-A high performance computer like Viper has a lot of elements of a desktop computer — processors, memory, disk, operating system — just more of them. High performance computers split off some of the tasks into separate elements to gain performance. An example of this on Viper is how it handles disk storage, which is a separate server with all of the storage directly connected to it. This is then connected across a very fast network to all of other individual computers (referred to as nodes).
+A high-performance computer like Viper has a lot of elements of a desktop computer — processors, memory, disk, operating system — just more of them. High-performance computers split off some of the tasks into separate elements to gain performance. An example of this on Viper is how it handles disk storage, which is a separate server with all of the storage directly connected to it. This is then connected across a very fast network to all of the other individual computers (referred to as nodes).
-Viper's real compute power is achieved by having a large amount of standard compute nodes ('''Compute'''), in our case 180 of them. Each of those nodes have 28 processing cores, so a total of 5040 processing cores ( i.e. 180 x 28 cores ). Some specialised nodes are included which are more suited to dedicated applications, such as high memory ('''Highmem''') nodes and GPU accelerator ('''GPU''') nodes which are particularly suited to large memory modelling and machine learning respectively.
+Viper's real compute power is achieved by having a large amount of standard compute nodes ('''Compute'''), in our case 180 of them. Each of those nodes has 28 processing cores, so a total of 5040 processing cores ( i.e. 180 x 28 cores ). Some specialised nodes are included which are more suited to dedicated applications, such as high memory ('''Highmem''') nodes and GPU accelerator ('''GPU''') nodes which are particularly suited to large memory modelling and machine learning respectively.
-The uses of supercomputers are wide spread and continue to be used in new and novel ways everyday.
+The uses of supercomputers are widespread and continue to be used in new and novel ways every day.
 Viper is used for
 * Astrophysics
-* Bio Engineering
+* BioEngineering
 * Business School
 * Chemistry
@@ Line 24: / Line 24: @@
 * Computation Linguistics
 * Geography
-* and many more
+* And many more
@@ Line 35: / Line 35: @@
 == Using Viper ==
-As a user when you login to Viper you will log into one of the two login nodes which will provide a Linux style command-line interface. From here it is possible to load modules (i.e. software), download data, compile code and submit jobs to the cluster. Note that the login node is not the computing cluster, this is accessed by submitting a job to the scheduler (SLURM).
+As a user when you log in to Viper you will log into one of the two login nodes which will provide a Linux style command-line interface. From here it is possible to load modules (i.e. software), download data, compile code and submit jobs to the cluster. Note that the login node is not the computing cluster, this is accessed by submitting a job to the scheduler (SLURM).
 === Module Add ===
@@ Line 43: / Line 43: @@
 === Batch Script ===
-This is a script which describes the parameters needed for the scheduler to submit you job to the compute cluster. For more information see [[general/Batch|batch jobs]].
+This is a script which describes the parameters needed for the scheduler to submit your job to the compute cluster. For more information see [[general/Batch|batch jobs]].
 === Batch Submission ===
@@ Line 55: / Line 55: @@
 == Queues available ==
-There are as previous mentioned 3 main queues that jobs to be sent to:
+There are as previously mentioned 3 main queues that jobs to be sent to:
 * compute - this queue will submit jobs to the 180 compute nodes
@@ Line 78: / Line 78: @@
 The compute nodes ('''compute''' and highmem ) are '''stateless''', with the GPU and visualisation node are statefull.
-* Note : the compute nodes that has no persistent operating system storage between boots (e.g. originates from hard drives being the persistent storage mechanism). Stateless nodes do not necessarily imply diskless, as ours have 128Gb SSD temporary space too.
+* Note: the compute nodes that have no persistent operating system storage between boots (e.g. originates from hard drives being the persistent storage mechanism). Stateless nodes do not necessarily imply diskless, as ours have 128Gb SSD temporary space too.

← Older revision		Revision as of 10:51, 17 June 2019
Line 30:		Line 30:

	* [https://viper.hull.ac.uk/ Apply for an account]		* [https://viper.hull.ac.uk/ Apply for an account]
−	* [[/General/Gallery What does Viper look like]]	+	* [[General/Gallery\|What does Viper look like?]]

← Older revision		Revision as of 10:50, 17 June 2019
Line 30:		Line 30:

	* [https://viper.hull.ac.uk/ Apply for an account]		* [https://viper.hull.ac.uk/ Apply for an account]
		+	* [[/General/Gallery What does Viper look like]]

← Older revision		Revision as of 10:49, 17 June 2019
Line 28:		Line 28:

	Like just about all other supercomputers Viper runs on [http://linux.co.uk Linux], which is similar to UNIX in many ways and has a wide body of software to support it.		Like just about all other supercomputers Viper runs on [http://linux.co.uk Linux], which is similar to UNIX in many ways and has a wide body of software to support it.
		+
		+	* [https://viper.hull.ac.uk/ Apply for an account]