How to run an interactive job on ARC - Revision history

Dmitri: /* Why not the login node? */

2024-09-27T17:53:30Z

Why not the login node?

← Older revision		Revision as of 17:53, 27 September 2024
Line 12:		Line 12:

	The '''login node''' could also be used to '''software development''', if you write scripts, or if you work on some new code for your research. The '''login node''', however, '''cannot be used''' to run anything that is CPU heavy and relates to '''research''', that is '''not management'''. See our[[General Cluster Guidelines and Policies#Login Node \| guidelines and policies]].		The '''login node''' could also be used to '''software development''', if you write scripts, or if you work on some new code for your research. The '''login node''', however, '''cannot be used''' to run anything that is CPU heavy and relates to '''research''', that is '''not management'''. See our[[General Cluster Guidelines and Policies#Login Node \| guidelines and policies]].


			The '''login node''' also has a '''limit on memory (RAM) of 5GB''' for all the processes of a single user.
			Sometimes this may be a limiting factor for interactive work.
			In such cases, even if the work fits the login node's design purpose, one has to request an '''interactive job''' to complete the work.

	= Submitting an interactive job =		= Submitting an interactive job =

Dmitri: /* Using the "single" partition */

2024-06-05T16:47:02Z

Using the "single" partition

← Older revision		Revision as of 16:47, 5 June 2024
Line 56:		Line 56:

	To request an interactive job on the single partition, you can use this command:		To request an interactive job on the single partition, you can use this command:
	$ salloc -N1 -n4 -c1 --mem=~~32GB~~ -t 5:00:00 -p single		$ salloc -N1 -n4 -c1 --mem=28GB -t 5:00:00 -p single

	This will give you an interactive resources for 5 hours.		This will give you an interactive resources for 5 hours.

Dmitri: /* Using the "single" partition */

2024-06-05T16:40:50Z

Using the "single" partition

← Older revision		Revision as of 16:40, 5 June 2024
Line 39:		Line 39:
	== Using the "single" partition ==		== Using the "single" partition ==

	The single partition does not offer much computing power, but designed to be almost always available for interactive work.		The '''single partition''' does not offer much computing power, but designed to be almost always available for '''interactive work'''.

	<pre>		<pre>
Line 59:		Line 59:

	This will give you an interactive resources for 5 hours.		This will give you an interactive resources for 5 hours.
			Please '''do not forget to end the job''' when you are done with either <Ctrl-D> keystroke or the exit command.

	= Downsides to interactive jobs =		= Downsides to interactive jobs =

Dmitri: /* Submitting an interactive job */

2024-06-05T16:39:29Z

Submitting an interactive job

← Older revision		Revision as of 16:39, 5 June 2024
Line 36:		Line 36:

	For '''GPU partitions and jobs''' please see its own [[How to request an interactive GPU on ARC \| How To article]].		For '''GPU partitions and jobs''' please see its own [[How to request an interactive GPU on ARC \| How To article]].

			== Using the "single" partition ==

			The single partition does not offer much computing power, but designed to be almost always available for interactive work.

			<pre>
			==========================================================================================
			Partition \| Nodes CPUs CPUs Memory (MB) GPUs Node list
			\| count total /node /node /node
			------------------------------------------------------------------------------------------
			single \| 14 224 16 120000 h[1-14]
			</pre>
			The nodes there have 16 CPUs and about 117GB of RAM each. There are 14 such nodes in the partition.

			The jobs are limited to 4 CPUs and 32GB of RAM. A user is limited to up to 2 such jobs at the same time.
			(You can run more jobs but the total limit on the resources is 8 CPUs and 64GB of RAM per user).
			Because of these limits it is difficult to make all the nodes busy with work and this is why
			there almost always some nodes available for interactive work.

			To request an interactive job on the single partition, you can use this command:
			$ salloc -N1 -n4 -c1 --mem=32GB -t 5:00:00 -p single

			This will give you an interactive resources for 5 hours.

	= Downsides to interactive jobs =		= Downsides to interactive jobs =

Dmitri: /* Background */

2024-03-18T18:40:14Z

Background

← Older revision		Revision as of 18:40, 18 March 2024
Line 3:		Line 3:


	'''Please note''', that '''interactive jobs''' on ARC should be limited to '''5 hours or less'''.		'''Please note''', that '''interactive jobs''' on ARC should be limited to '''5 hours or less''' of requested run time.

	= Why not the login node? =		= Why not the login node? =

Dmitri: /* Background */

2024-03-18T18:39:54Z

Background

← Older revision		Revision as of 18:39, 18 March 2024
Line 1:		Line 1:
	= Background =		= Background =
	Submitting and running jobs is the only way to run computations on ARC. Normally, a user creates a '''job script''' and submit it to SLURM on ARC using the <code>sbatch</code> command to run a computation. This type of jobs are non-interactive batch jobs. In some circumstances, this type of workflow may be difficult or incompatible with workflows that require interactive inputs by the user such as when you need to apply data transformation, result collection and review from large computations, or to test new methods or software. For this kind of work, the best approach is to request an '''interactive job''' from ARC's.		Submitting and running jobs is the only way to run computations on ARC. Normally, a user creates a '''job script''' and submit it to SLURM on ARC using the <code>sbatch</code> command to run a computation. This type of jobs are non-interactive batch jobs. In some circumstances, this type of workflow may be difficult or incompatible with workflows that require interactive inputs by the user such as when you need to apply data transformation, result collection and review from large computations, or to test new methods or software. For this kind of work, the best approach is to request an '''interactive job''' from ARC's.


			'''Please note''', that '''interactive jobs''' on ARC should be limited to '''5 hours or less'''.

	= Why not the login node? =		= Why not the login node? =

Dmitri: /* Downsides to interactive jobs */

2024-02-06T20:29:05Z

Downsides to interactive jobs

← Older revision		Revision as of 20:29, 6 February 2024
Line 50:		Line 50:

	Please remember that interactive jobs is '''not intended to be the primary way''' of using the ARC cluster.		Please remember that interactive jobs is '''not intended to be the primary way''' of using the ARC cluster.

			= Links =
			[[How-Tos]]

	[[Category:Guides]]		[[Category:Guides]]

Dmitri at 18:51, 31 January 2024

2024-01-31T18:51:27Z

Dmitri at 18:51, 31 January 2024

2024-01-31T18:51:06Z

← Older revision		Revision as of 18:51, 31 January 2024
Line 1:		Line 1:
			= Background =
	Submitting and running jobs is the only way to run computations on ARC. Normally, a user creates a '''job script''' and submit it to SLURM on ARC using the <code>sbatch</code> command to run a computation. This type of jobs are non-interactive batch jobs. In some circumstances, this type of workflow may be difficult or incompatible with workflows that require interactive inputs by the user such as when you need to apply data transformation, result collection and review from large computations, or to test new methods or software. For this kind of work, the best approach is to request an '''interactive job''' from ARC's.		Submitting and running jobs is the only way to run computations on ARC. Normally, a user creates a '''job script''' and submit it to SLURM on ARC using the <code>sbatch</code> command to run a computation. This type of jobs are non-interactive batch jobs. In some circumstances, this type of workflow may be difficult or incompatible with workflows that require interactive inputs by the user such as when you need to apply data transformation, result collection and review from large computations, or to test new methods or software. For this kind of work, the best approach is to request an '''interactive job''' from ARC's.

	== Why not the login node? ==		= Why not the login node? ==
	The login node is designed for users to interactively use ARC. However, this usage is intended for only '''management work''', such as:		The login node is designed for users to interactively use ARC. However, this usage is intended for only '''management work''', such as:
	* data management,		* data management,
Line 9:		Line 10:
	The '''login node''' could also be used to '''software development''', if you write scripts, or if you work on some new code for your research. The '''login node''', however, '''cannot be used''' to run anything that is CPU heavy and relates to '''research''', that is '''not management'''. See our[[General Cluster Guidelines and Policies#Login Node \| guidelines and policies]].		The '''login node''' could also be used to '''software development''', if you write scripts, or if you work on some new code for your research. The '''login node''', however, '''cannot be used''' to run anything that is CPU heavy and relates to '''research''', that is '''not management'''. See our[[General Cluster Guidelines and Policies#Login Node \| guidelines and policies]].

	== Submitting an interactive job ==		= Submitting an interactive job ==

	To '''request an interactive job''' on ARC via SLURM, you have to use the <code>salloc</code> command and		To '''request an interactive job''' on ARC via SLURM, you have to use the <code>salloc</code> command and
Line 33:		Line 34:
	For '''GPU partitions and jobs''' please see its own [[How to request an interactive GPU on ARC \| How To article]].		For '''GPU partitions and jobs''' please see its own [[How to request an interactive GPU on ARC \| How To article]].

	== Downsides to interactive jobs ==		= Downsides to interactive jobs ==
	However, one has to remember that there are some '''negatives''' of using '''interactive jobs''':		However, one has to remember that there are some '''negatives''' of using '''interactive jobs''':
	* '''Resource utilization''' is typically '''quite low''' when compared with non-interactive jobs.		* '''Resource utilization''' is typically '''quite low''' when compared with non-interactive jobs.

Dmitri at 18:49, 31 January 2024

2024-01-31T18:49:49Z

← Older revision		Revision as of 18:49, 31 January 2024
Line 53:		Line 53:
	[[Category:How-Tos]]		[[Category:How-Tos]]
	[[Category:ARC]]		[[Category:ARC]]
			{{Navbox ARC}}

← Older revision		Revision as of 18:51, 31 January 2024
Line 2:		Line 2:
	Submitting and running jobs is the only way to run computations on ARC. Normally, a user creates a '''job script''' and submit it to SLURM on ARC using the <code>sbatch</code> command to run a computation. This type of jobs are non-interactive batch jobs. In some circumstances, this type of workflow may be difficult or incompatible with workflows that require interactive inputs by the user such as when you need to apply data transformation, result collection and review from large computations, or to test new methods or software. For this kind of work, the best approach is to request an '''interactive job''' from ARC's.		Submitting and running jobs is the only way to run computations on ARC. Normally, a user creates a '''job script''' and submit it to SLURM on ARC using the <code>sbatch</code> command to run a computation. This type of jobs are non-interactive batch jobs. In some circumstances, this type of workflow may be difficult or incompatible with workflows that require interactive inputs by the user such as when you need to apply data transformation, result collection and review from large computations, or to test new methods or software. For this kind of work, the best approach is to request an '''interactive job''' from ARC's.

	= Why not the login node? ==		= Why not the login node? =
	The login node is designed for users to interactively use ARC. However, this usage is intended for only '''management work''', such as:		The login node is designed for users to interactively use ARC. However, this usage is intended for only '''management work''', such as:
	* data management,		* data management,
Line 10:		Line 10:
	The '''login node''' could also be used to '''software development''', if you write scripts, or if you work on some new code for your research. The '''login node''', however, '''cannot be used''' to run anything that is CPU heavy and relates to '''research''', that is '''not management'''. See our[[General Cluster Guidelines and Policies#Login Node \| guidelines and policies]].		The '''login node''' could also be used to '''software development''', if you write scripts, or if you work on some new code for your research. The '''login node''', however, '''cannot be used''' to run anything that is CPU heavy and relates to '''research''', that is '''not management'''. See our[[General Cluster Guidelines and Policies#Login Node \| guidelines and policies]].

	= Submitting an interactive job ==		= Submitting an interactive job =

	To '''request an interactive job''' on ARC via SLURM, you have to use the <code>salloc</code> command and		To '''request an interactive job''' on ARC via SLURM, you have to use the <code>salloc</code> command and
Line 34:		Line 34:
	For '''GPU partitions and jobs''' please see its own [[How to request an interactive GPU on ARC \| How To article]].		For '''GPU partitions and jobs''' please see its own [[How to request an interactive GPU on ARC \| How To article]].

	= Downsides to interactive jobs ==		= Downsides to interactive jobs =
	However, one has to remember that there are some '''negatives''' of using '''interactive jobs''':		However, one has to remember that there are some '''negatives''' of using '''interactive jobs''':
	* '''Resource utilization''' is typically '''quite low''' when compared with non-interactive jobs.		* '''Resource utilization''' is typically '''quite low''' when compared with non-interactive jobs.