Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • gpaw gpaw
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 290
    • Issues 290
    • List
    • Boards
    • Service Desk
    • Milestones
    • Requirements
  • Merge requests 113
    • Merge requests 113
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpawgpaw
  • gpawgpaw
  • Issues
  • #614
Closed
Open
Issue created Oct 14, 2022 by Vladislav Ivanistsev@vladislav.ivanistsevDeveloper

Inconsistance in estimated and used memory

I see inconsistent set of numbers for estimated and used memory.

Here is an example for exactly the same model with variable parallelization numbers of kpts, domain, and band.

You can run the script as:

gpaw python input.py K_B_D_KPTS_VAC_CUTOFF

where K, B, and D are parallelization numbers of kpts, domain, and band; KPTS, VAC, and CUTOFF are parameters of the model – k_x,y-points, vacuum, and PW cutoff.

For example:

gpaw python input.py 2_4_2_2_4_340

I also attach a slurm submission script.

input.py

submit.sh

The estimated memory is from "Memory estimate: Calculator: VALUE" and the used memory is from the "Memory usage: VALUE" of the standard output file.

The minor issue is the inconstancy in units – it is better to give both memory values in Mb.

The major issue is the inverse correlation of estimated memory vs used memory (15 points for various combination of K×D×B = 16):

image

Either I am doing something very wrong – please correct me – or there is a bug in memory estimation. In both cases, I am eager to help.

P.S. I am using GPAW 22.8 from conda-forge. All other parameters are in the files.

Edited Oct 14, 2022 by Vladislav Ivanistsev
Assignee
Assign to
Time tracking