Getting Started - Revision history

Daniel-schurhoff-de23@rwth-aachen.de at 13:06, 3 September 2019

2019-09-03T13:06:46Z

Daniel-schurhoff-de23@rwth-aachen.de at 13:03, 3 September 2019

2019-09-03T13:03:53Z

Stefan-erlbeck-05df@rwth-aachen.de: Changed the title reference of Schedulers to Scheduling_Basics, because someone reading 'getting started' may like to read more about the fundamentals

2018-11-14T12:18:49Z

Changed the title reference of Schedulers to Scheduling_Basics, because someone reading 'getting started' may like to read more about the fundamentals

Daniel-schurhoff-de23@rwth-aachen.de at 12:19, 13 November 2018

2018-11-13T12:19:57Z

Daniel-schurhoff-de23@rwth-aachen.de at 08:22, 2 October 2018

2018-10-02T08:22:14Z

Ds019135 at 15:22, 31 July 2018

2018-07-31T15:22:32Z

Ds019135 at 15:22, 31 July 2018

2018-07-31T15:22:24Z

Ds019135 at 15:20, 31 July 2018

2018-07-31T15:20:18Z

Ds019135 at 15:20, 31 July 2018

2018-07-31T15:20:10Z

Christian-wassermann-e30b@rwth-aachen.de at 14:12, 16 April 2018

2018-04-16T14:12:36Z

@@ Line 1: / Line 1: @@
 [[Category:Basics]]
 == [[Access|Access]] or "How-to-be-allowed-onto-the-supercomputer" ==
 Depending on the specific supercomputer, one has to either register to get a user account or write a project proposal and apply for computing resources that way. The respective pages are linked in [[Access|this overview]].

← Older revision		Revision as of 13:03, 3 September 2019
Line 1:		Line 1:
		+	[[Category:Basics]]
		+
	== [[Access\|Access]] or "How-to-be-allowed-onto-the-supercomputer" ==		== [[Access\|Access]] or "How-to-be-allowed-onto-the-supercomputer" ==
	Depending on the specific supercomputer, one has to either register to get a user account or write a project proposal and apply for computing resources that way. The respective pages are linked in [[Access\|this overview]].		Depending on the specific supercomputer, one has to either register to get a user account or write a project proposal and apply for computing resources that way. The respective pages are linked in [[Access\|this overview]].

@@ Line 19: / Line 19: @@
 A little bit more information can be found in the [[File_Transfer|File Transfer]] article.
-== [[Schedulers|Schedulers]] or "How-To-Run-Applications-on-a-supercomputer" ==
+== [[Scheduling_Basics|Schedulers]] or "How-To-Run-Applications-on-a-supercomputer" ==
 To run any significant program or workload on a supercomputer, generally a [[Scheduling_Basics|Batch-Scheduler]] is employed. Alongside the above-mentioned Login Nodes there are usually far more Backend Nodes in the system (computers exclusively reserved for computing, to which you cannot connect directly, also referred to as "batch system"). A program called Batch-scheduler decides who gets how many of those compute resources for which amount of time. Please use the Backend Nodes for everything which is not a simple small test and only runs for a few minutes., otherwise you will block the Login Nodes for everybody when you run your calculations there. These Backend Nodes make up more than 98% of a supercomputer and can only be accessed via the scheduler.

@@ Line 20: / Line 20: @@
 == [[Schedulers|Schedulers]] or "How-To-Run-Applications-on-a-supercomputer" ==
-To run any significant program or workload on a supercomputer, generally a [[Batch-Scheduler|Batch-Scheduler]] is employed. Alongside the above-mentioned Login Nodes there are usually far more Backend Nodes in the system (computers exclusively reserved for computing, to which you cannot connect directly, also referred to as "batch system"). A program called Batch-scheduler decides who gets how many of those compute resources for which amount of time. Please use the Backend Nodes for everything which is not a simple small test and only runs for a few minutes., otherwise you will block the Login Nodes for everybody when you run your calculations there. These Backend Nodes make up more than 98% of a supercomputer and can only be accessed via the scheduler.
+To run any significant program or workload on a supercomputer, generally a [[Scheduling_Basics|Batch-Scheduler]] is employed. Alongside the above-mentioned Login Nodes there are usually far more Backend Nodes in the system (computers exclusively reserved for computing, to which you cannot connect directly, also referred to as "batch system"). A program called Batch-scheduler decides who gets how many of those compute resources for which amount of time. Please use the Backend Nodes for everything which is not a simple small test and only runs for a few minutes., otherwise you will block the Login Nodes for everybody when you run your calculations there. These Backend Nodes make up more than 98% of a supercomputer and can only be accessed via the scheduler.
 When you log into a supercomputer, you can run commands on the Login Nodes interactively. You type, you hit return, the command gets executed. Schedulers work differently. You submit a series of commands (in form of a file) and tell it, how much resources it will approximately need in terms of:

@@ Line 19: / Line 19: @@
 A little bit more information can be found in the [[File_Transfer|File Transfer]] article.
-== [[Scheduler|Schedulers]] or "How-To-Run-Applications-on-a-supercomputer" ==
+== [[Schedulers|Schedulers]] or "How-To-Run-Applications-on-a-supercomputer" ==
-To run any significant program or workload on a supercomputer, generally [[Scheduler|schedulers]] are employed. Alongside the above-mentioned Login Nodes there are usually far more Backend Nodes in the system (computers exclusively reserved for computing, to which you cannot connect directly, also referred to as "batch system"). A program called scheduler decides who gets how many of those compute resources for which amount of time. Please use the Backend Nodes for everything which is not a simple small test and only runs for a few minutes., otherwise you will block the Login Nodes for everybody when you run your calculations there. These Backend Nodes make up more than 98% of a supercomputer and can only be accessed via the scheduler.
+To run any significant program or workload on a supercomputer, generally a [[Batch-Scheduler|Batch-Scheduler]] is employed. Alongside the above-mentioned Login Nodes there are usually far more Backend Nodes in the system (computers exclusively reserved for computing, to which you cannot connect directly, also referred to as "batch system"). A program called Batch-scheduler decides who gets how many of those compute resources for which amount of time. Please use the Backend Nodes for everything which is not a simple small test and only runs for a few minutes., otherwise you will block the Login Nodes for everybody when you run your calculations there. These Backend Nodes make up more than 98% of a supercomputer and can only be accessed via the scheduler.
 When you log into a supercomputer, you can run commands on the Login Nodes interactively. You type, you hit return, the command gets executed. Schedulers work differently. You submit a series of commands (in form of a file) and tell it, how much resources it will approximately need in terms of:

← Older revision		Revision as of 15:22, 31 July 2018
Line 1:		Line 1:
−	~~asdf~~
	== [[Access\|Access]] or "How-to-be-allowed-onto-the-supercomputer" ==		== [[Access\|Access]] or "How-to-be-allowed-onto-the-supercomputer" ==
	Depending on the specific supercomputer, one has to either register to get a user account or write a project proposal and apply for computing resources that way. The respective pages are linked in [[Access\|this overview]].		Depending on the specific supercomputer, one has to either register to get a user account or write a project proposal and apply for computing resources that way. The respective pages are linked in [[Access\|this overview]].

← Older revision		Revision as of 15:20, 31 July 2018
Line 1:		Line 1:
−	~~test~~
	== [[Access\|Access]] or "How-to-be-allowed-onto-the-supercomputer" ==		== [[Access\|Access]] or "How-to-be-allowed-onto-the-supercomputer" ==
	Depending on the specific supercomputer, one has to either register to get a user account or write a project proposal and apply for computing resources that way. The respective pages are linked in [[Access\|this overview]].		Depending on the specific supercomputer, one has to either register to get a user account or write a project proposal and apply for computing resources that way. The respective pages are linked in [[Access\|this overview]].

← Older revision		Revision as of 14:12, 16 April 2018
Line 53:		Line 53:

	== [[Parallel_Programming\|Parallel Programming]] or "How-To-Use-More-Than-One-Core" ==		== [[Parallel_Programming\|Parallel Programming]] or "How-To-Use-More-Than-One-Core" ==
−	Currently development of computers is at a point, where you cannot just make a processor run faster, because ~~the~~ semiconductor ~~physics simply do not work that way~~. Therefore the current approach is to split the work into multiple, ideally independent parts, which are then executed in parallel. Similar to cleaning your house, where everybody takes care of a few rooms, on a supercomputer this is usually done with parallel programming paradigms like [[OpenMP\|Open Multi-Processing (OpenMP)]] or [[MPI\|Message Passing Interface (MPI)]]. However like the fact that you only have one vacuum cleaner in the whole house which not everybody can use at the same time, there are limits on how fast you can get, even with a big number of processing units/cpus/cores (analogous to people in the metaphor) working on your problem (cleaning the house) in parallel.	+	Currently development of computers is at a point, where you cannot just make a processor run faster (e.g. by increasing its clock frequency), because limits of physics have been reached in semiconductor development. Therefore the current approach is to split the work into multiple, ideally independent parts, which are then executed in parallel. Similar to cleaning your house, where everybody takes care of a few rooms, on a supercomputer this is usually done with parallel programming paradigms like [[OpenMP\|Open Multi-Processing (OpenMP)]] or [[MPI\|Message Passing Interface (MPI)]]. However like the fact that you only have one vacuum cleaner in the whole house which not everybody can use at the same time, there are limits on how fast you can get, even with a big number of processing units/cpus/cores (analogous to people in the metaphor) working on your problem (cleaning the house) in parallel.