Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
hpc-compendium
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
ZIH
hpcsupport
hpc-compendium
Merge requests
!464
Add way to gather max. mem from the job
Code
Review changes
Check out branch
Download
Patches
Plain diff
Merged
Add way to gather max. mem from the job
max-mem
into
preview
Overview
0
Commits
3
Pipelines
0
Changes
1
Merged
Martin Schroschk
requested to merge
max-mem
into
preview
3 years ago
Overview
0
Commits
3
Pipelines
0
Changes
1
Expand
0
0
Merge request reports
Compare
preview
version 2
1ad7c335
3 years ago
version 1
fcc0b2f8
3 years ago
preview (base)
and
latest version
latest version
70f3d673
3 commits,
3 years ago
version 2
1ad7c335
2 commits,
3 years ago
version 1
fcc0b2f8
1 commit,
3 years ago
1 file
+
35
−
0
Side-by-side
Compare changes
Side-by-side
Inline
Show whitespace changes
Show one file at a time
doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm_profiling.md
+
35
−
0
Options
@@ -60,3 +60,38 @@ More information about profiling with Slurm:
@@ -60,3 +60,38 @@ More information about profiling with Slurm:
-
[
Slurm Profiling
](
http://slurm.schedmd.com/hdf5_profile_user_guide.html
)
-
[
Slurm Profiling
](
http://slurm.schedmd.com/hdf5_profile_user_guide.html
)
-
[
`sh5util`
](
http://slurm.schedmd.com/sh5util.html
)
-
[
`sh5util`
](
http://slurm.schedmd.com/sh5util.html
)
## Memory Consumption of a Job
If you are only interested in the maximal memory consumption of your job, you don't need profiling
at all. This information can be retrieved from within
[
job files
](
slurm.md#batch-jobs
)
as follows:
```
bash
#!/bin/bash
#SBATCH [...]
module purge
module load
[
...]
srun a.exe
# Retrieve max. memory for this job for all nodes
srun max_mem.sh
```
The script
`max_mem.sh`
is:
```
bash
#!/bin/bash
echo
-n
"
$(
hostname
)
: "
cat
/sys/fs/cgroup/memory/slurm/uid_
${
SLURM_JOB_UID
}
/job_
${
SLURM_JOB_ID
}
/memory.max_usage_in_bytes
```
!!! note
*
Make sure that the script
`max_mem.sh`
is executable (e.g.,
`chmod +x max_mem.sh`
) and add the
path to this script if it is not within the same directory.
*
The
`srun`
command is necessary to gather the max. memory from all nodes within this job.
Otherwise, you would only get the data from one node.
Loading