MAXMEM: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{TAGDEF|MAXMEM|[integer]|2800 (VASP 5.4.4. and older) | {{TAGDEF|MAXMEM|[integer]|2800 (VASP.5.4.4. and older), automatically set as of VASP.6 }} | ||
Description: {{TAG|MAXMEM}} specifies the maximum memory one MPI rank will attempt to allocate (in MByte). | Description: {{TAG|MAXMEM}} specifies the maximum memory one MPI rank will attempt to allocate (in MByte). | ||
| Line 13: | Line 13: | ||
== Related Tags and Sections == | == Related Tags and Sections == | ||
[[GW calculations]] | [[GW calculations]] | ||
[[NTAUPAR]] | |||
{{sc|MAXMEM | {{sc|MAXMEM|Examples|Examples that use this tag}} | ||
---- | ---- | ||
[[Category:INCAR]][[Category:Many-Body Perturbation Theory]][[Category:GW]][[Category:Low-scaling GW and RPA]] | [[Category:INCAR]][[Category:Many-Body Perturbation Theory]][[Category:GW]][[Category:Low-scaling GW and RPA]][[Category: VASP6]] | ||
Revision as of 11:24, 12 August 2019
MAXMEM = [integer]
Default: MAXMEM = 2800 (VASP.5.4.4. and older), automatically set as of VASP.6
Description: MAXMEM specifies the maximum memory one MPI rank will attempt to allocate (in MByte). Since, the default varies somewhat between VASP versions, it is safer to set this flag manually. Currently the flag is only inspected in few selected routines, such as the GW or RPA routines that can use excessive amounts of memory. It is recommended to set MAXMEM to the available memory per core minus 200 Mbyte. For instance, if one node is equipped with 12 Gbyte, and 6 MPI ranks share this memory, the recommended setting is 12*1024/6-200 = 1848.
As of VASP.6 the default value of MAXMEM is set to 90 percent of the available memory per MPI rank of the node. If more than one computation node is used, the minimum of all nodes is used.