Memory Issue with ALGO=ACFDTR

Problems running VASP: crashes, internal errors, "wrong" results.

Moderators: Global Moderator, Moderator

Post Reply
Message
Author
s_ringe
Newbie
Newbie
Posts: 3
Joined: Wed Jul 20, 2022 8:07 am

Memory Issue with ALGO=ACFDTR

#1 Post by s_ringe » Wed Dec 07, 2022 10:08 am

Dear developers,

I ran into an unexpected memory usage problem while calculating RPA using ALGO=ACFDTR.

In the calculation using 56 processes per node, the memory usage after assigning 28 processes to each node is more than twice as large as the memory usage after giving 56 processes to one node.

In the calculation using one node, each process consumes approximately 2 gigabytes of memory, so I expected similar or slightly larger memory usage (because of the communication buffer between nodes) for two or more nodes, but more than double (approximately 6 gigabytes) I thought the usage was abnormal.

After checking the memory through OUTCAR as well as directly through the terminal, I found that this was not just a reporting issue.

Below is the INCAR that I used.

Code: Select all

NPAR = 56; KPAR = 1

ALGO = ACFDTR; PREC = Accurate; ISTART = 1

ENCUT = 400; ISMEAR = 0; SIGMA = 0.05

NBANDS = 7952

NOMEGA = 24; ENCUTGW = 200

LWAVE = .FALSE.; LCHARG = .FALSE.
Thanks.

s_ringe
Newbie
Newbie
Posts: 3
Joined: Wed Jul 20, 2022 8:07 am

Re: Memory Issue with ALGO=ACFDTR

#2 Post by s_ringe » Wed Dec 07, 2022 4:17 pm

Dear developers,

For reference, the calculation environment is as follows.

Operating System: Rocky Linux 8.4 (Green Obsidian), Linux 4.18.0-305.el8.x86_64
Compiler: ifort (IFORT) 2021.5.0 20211109
openmpi, oneapi, and hdf5 used

Thanks.

merzuk.kaltak
Administrator
Administrator
Posts: 190
Joined: Mon Sep 24, 2018 9:39 am

Re: Memory Issue with ALGO=ACFDTR

#3 Post by merzuk.kaltak » Fri Dec 09, 2022 12:58 pm

Dear s_ringe,

judging from your INCAR, the memory requirement is estimated automatically.
This happens "under the hood" so to speak. On a Linux machine VASP looks into /proc/meminfo for the entry MemAvailable and sets MAXMEM automatically. This value of MAXMEM is used internally to set NTAUPAR which ultimately influences how much memory is used.
Note, by default VASP is quite "greedy" and grabs 90 percent of available RAM for the each run.

I suspect that NTAUPAR is higher for the job with 28 MPI ranks and thus uses more memory. However, I can say more if you upload a proper error report.

s_ringe
Newbie
Newbie
Posts: 3
Joined: Wed Jul 20, 2022 8:07 am

Re: Memory Issue with ALGO=ACFDTR

#4 Post by s_ringe » Fri Dec 09, 2022 2:54 pm

Dear merzuk.kaltak,


Thank you so much for your valuable comments!

I checked the output and saw that NTAUPAR had a larger value when using 28 processes. :D


Thank you and Best Regards,

s_ringe

Post Reply