Development/Vampir and VampirServer - Revision history

S Richling at 22:58, 8 December 2022

2022-12-08T22:58:21Z

← Older revision		Revision as of 00:58, 9 December 2022
Line 224:		Line 224:
	\| Print VampirServer's revision		\| Print VampirServer's revision
	\|}		\|}

	[[Category:performance analysis software]]

S Richling at 22:58, 8 December 2022

2022-12-08T22:58:05Z

← Older revision		Revision as of 00:58, 9 December 2022
Line 36:		Line 36:

	Application traces consist of information gathered on the clusters prior to running Vampir		Application traces consist of information gathered on the clusters prior to running Vampir
	using VampirTrace or [[Score-P]] and include timing, MPI communication, MPI I/O, hardware performance counters		using VampirTrace or [[Development/Score-P\|Score-P]] and include timing, MPI communication, MPI I/O, hardware performance counters
	and CUDA / OpenCL profiling (if enabled in the tracing library).		and CUDA / OpenCL profiling (if enabled in the tracing library).

Line 59:		Line 59:
	provides Manuals in the <kbd>$VAMPIR_DOC_DIR</kbd> directory.		provides Manuals in the <kbd>$VAMPIR_DOC_DIR</kbd> directory.

	Prior to analyzing your application, You need to compile and link with [[Score-P]].		Prior to analyzing your application, You need to compile and link with [[Development/Score-P\|Score-P]].

	== Running Vampir GUI ==		== Running Vampir GUI ==
Line 153:		Line 153:

	== How to navigate Vampir GUI ==		== How to navigate Vampir GUI ==
	This section is by no means a complete tutorial, however one may follow the general concepts by tracing one's application using [[Score-P]] or by downloading the [https://vampir.eu/public/files/tracefiles/Large_Score-P.zip Large Scale Score-P WRF trace].		This section is by no means a complete tutorial, however one may follow the general concepts by tracing one's application using [[Development/Score-P\|Score-P]] or by downloading the [https://vampir.eu/public/files/tracefiles/Large_Score-P.zip Large Scale Score-P WRF trace].

	[[File:vampirscreen.png\|896px\|frame\|Vampir Screen using Dark Mode]]		[[File:vampirscreen.png\|896px\|frame\|Vampir Screen using Dark Mode]]

S Richling: S Richling moved page Vampir and VampirServer to Development/Vampir and VampirServer: Umzug in Developmentbereich

2022-12-08T22:53:02Z

S Richling moved page Vampir and VampirServer to Development/Vampir and VampirServer: Umzug in Developmentbereich

← Older revision	Revision as of 00:53, 9 December 2022
(No difference)

H Winkhardt at 14:00, 21 December 2021

2021-12-21T14:00:33Z

← Older revision		Revision as of 16:00, 21 December 2021
Line 1:		Line 1:
	{{Softwarepage}}		{{Softwarepage\|devel/vampir}}

	{\| width=600px class="wikitable"		{\| width=600px class="wikitable"

H Winkhardt at 10:53, 16 December 2021

2021-12-16T10:53:00Z

← Older revision		Revision as of 12:53, 16 December 2021
Line 29:		Line 29:

	If You want to make usage of a local installation as described in [[#Running Vampir GUI locally with parallel VampirServer\|the section below]], please contact your Universities local compute center or by mail to [mailto:cluster-support@hs-esslingen.de cluster-support@hs-esslingen.de].		If You want to make usage of a local installation as described in [[#Running Vampir GUI locally with parallel VampirServer\|the section below]], please contact your Universities local compute center or by mail to [mailto:cluster-support@hs-esslingen.de cluster-support@hs-esslingen.de].

	On March 18th 2021, we will host an Online-Workshop "Performance Analyse mit Vampir und Score-P", the slides are available HERE.
	<br>		<br>

H Winkhardt at 09:28, 16 December 2021

2021-12-16T09:28:30Z

@@ Line 1: / Line 1: @@
 {| width=600px class="wikitable"
 |-
@@ Line 5: / Line 7: @@
 | module load
 | devel/vampir
 |-
 | License
@@ Line 35: / Line 34: @@
 = Versions and Availability =
 Vampir provides the GUI and allows analyzing traces of a few hundred Megabytes. For larger traces, you may want
 to revert to using a remote VampirServer running in parallel on the compute nodes via a Batch script (see below).

R Keller: Add caveat of Vampir-10.0 vs. Vampir-9.x

2021-12-13T12:31:28Z

Add caveat of Vampir-10.0 vs. Vampir-9.x

← Older revision		Revision as of 14:31, 13 December 2021
Line 58:		Line 58:
	$ module avail devel/vampir		$ module avail devel/vampir
	------------------------ /opt/bwhpc/common/modulefiles/Core -------------------------		------------------------ /opt/bwhpc/common/modulefiles/Core -------------------------
	devel/vampir/9.9</pre>		devel/vampir/10.0</pre>

	<font color=red>Attention!</font><br>		<font color=red>Attention!</font><br>
	Do not run <kbd>vampir</kbd> or <kbd>vampirserver</kbd> on the head nodes with large traces with many analysis processes for a long period of time.		Do not run <kbd>vampir</kbd> or <kbd>vampirserver</kbd> on the head nodes with large traces with many analysis processes for a long period of time.
	Instead use one of the possibilities listed below.		Instead use one of the possibilities listed below.
			<br>

			<font color=red>Please note:</font><br>
			The <kbd>vampirserver</kbd> v10.0 protocol is not compatible to Vampir v9.x GUI, i.e. you will need to install matching versions on your
			local work-place PC. Please contact your computer center for installation files.
	<br>		<br>

K Siegmund at 18:18, 3 December 2021

2021-12-03T18:18:33Z

← Older revision		Revision as of 20:18, 3 December 2021
Line 235:		Line 235:
	\|}		\|}

	[[Category:performance analysis software~~]][[Category:bwUniCluster]][[Category:bwForCluster~~]]		[[Category:performance analysis software]]

R Keller: /* Running Vampir GUI with parallel VampirServer */

2021-03-18T20:30:02Z

Running Vampir GUI with parallel VampirServer

← Older revision		Revision as of 22:30, 18 March 2021
Line 95:		Line 95:
	<pre>		<pre>
	bwunicluster$ module load devel/vampir		bwunicluster$ module load devel/vampir
	bwunicluster$ ~~sbatch~~ --~~time=02:00:00~~ ~~$VAMPIR_HOME/vampirserver.slurm~~		bwunicluster$ vampirserver start -- -t 60
			Launching VampirServer...
	Submitted batch job 1234
			Submitting slurm 60 minutes job (this might take a while)...
	</pre>		</pre>
	Please note that this submits a minimal batch allocation to queue <kbd>multiple</kbd>.		Please note that this submits a minimal batch allocation to queue <kbd>multiple</kbd>.
	Since this may take considerable amount to start (like 10 minutes to an hour), start another batch job ~~but to the queue~~ mainly aimed at testing and ~~developping~~:		Since this may take considerable amount to start (like 10 minutes to an hour), start another batch job mainly aimed at testing and developing:
	<pre>		<pre>
	bwunicluster$ ~~sbatch~~ --~~partition=dev_multiple~~ -~~-time=~~30 ~~$VAMPIR_HOME/vampirserver.slurm~~		bwunicluster$ vampirserver start -- -t 30 -- --partition=dev_multiple
			Launching VampirServer...
	Submitted batch job 1235
			Submitting slurm 30 minutes job (this might take a while)...
			salloc: Pending job allocation 19393903
			salloc: job 1234 queued and waiting for resources
			salloc: job 1234 has been allocated resources
			salloc: Granted job allocation 1234
			salloc: Waiting for resource configuration
			salloc: Nodes uc2n[001-002] are ready for job
			VampirServer 9.10.0 (5886afc1)
			Licensed to Universitäten und Hochschulen Baden-Württemberg
			Running 4 analysis processes... (abort with vampirserver stop 567)
			VampirServer <567> listens on: uc2n001.localdomain:30000
	</pre>		</pre>
	The maximum amount of time is 30 minutes in this queue (on bwUniCluster check [[BwUniCluster_2.0_Batch_Queues]]).		The maximum amount of time is 30 minutes in this queue (on bwUniCluster check [[BwUniCluster_2.0_Batch_Queues]]).
Line 108:		Line 120:

	'''Please note:'''		'''Please note:'''
			* You may list running VampirServer using <kbd>vampirserver ls</kbd>,
	* Check <kbd>squeue</kbd> and files <kbd>slurm-1234.out</kbd> and <kbd>slurm-1235.out</kbd> for node and port info to connect to remotely,
			* You may now connect to the VampirServer from the Vampir GUI using the above node <kbd>uc2n001</kbd> and port <kbd>30000</kbd>,
	* Having trace files stored on the compute nodes SSDs may help performance '''if they already''' are there; otherwise VampirServer will load trace files in memory from the file system upon receiving the load-command from Vampir GUI,		* Having trace files stored on the compute nodes SSDs may help performance '''if they already''' are there; otherwise VampirServer will load trace files in memory from the file system upon receiving the load-command from Vampir GUI,
	* Disconnecting from a remote VampirServer does not quit or cancel the job,		* Disconnecting from a remote VampirServer does not quit or cancel the batch job,
	* In case Your VampirServer batch job runs out of time, You'll receive a "connetion closed" failure,		* In case Your VampirServer batch job runs out of time, You'll receive a "connetion closed" failure in Vampir GUI,
	* Please '''free''' resources of a running VampirServer using <kbd>scancel 1234</kbd> if finished,		* Please '''free''' resources of a running VampirServer using <kbd>scancel 1234</kbd> if finished,
	* More information on VampirServer is provided in the below section.		* More information on VampirServer is provided in the below section.

R Keller: /* Introduction */

2021-03-18T16:05:19Z

Introduction

← Older revision		Revision as of 18:05, 18 March 2021
Line 31:		Line 31:
	If You want to make usage of a local installation as described in [[#Running Vampir GUI locally with parallel VampirServer\|the section below]], please contact your Universities local compute center or by mail to [mailto:cluster-support@hs-esslingen.de cluster-support@hs-esslingen.de].		If You want to make usage of a local installation as described in [[#Running Vampir GUI locally with parallel VampirServer\|the section below]], please contact your Universities local compute center or by mail to [mailto:cluster-support@hs-esslingen.de cluster-support@hs-esslingen.de].

	On March 18th 2021, we will host an Online-Workshop "Performance Analyse mit Vampir und Score-P".		On March 18th 2021, we will host an Online-Workshop "Performance Analyse mit Vampir und Score-P", the slides are available HERE.
	<br>		<br>