MAXMEM: Difference between revisions
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
Description: {{TAG|MAXMEM}} specifies the maximum memory one core will attempt to allocate (in MByte). | Description: {{TAG|MAXMEM}} specifies the maximum memory one core 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 | flag manually. Currently the flag is only inspected in few selected routines, such as | ||
the GW routines | 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 | MAXMEM to the available memory per core minus 200 Mbyte. For instance, if one node is equipped | ||
with 12 Gbyte, and 6 cores share this memory, the recommended setting is 12000/6-200 = 1800. | with 12 Gbyte, and 6 cores share this memory, the recommended setting is 12000/6-200 = 1800. | ||
Revision as of 17:50, 13 March 2017
MAXMEM = [integer]
Default: MAXMEM = 2800
Description: MAXMEM specifies the maximum memory one core 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 cores share this memory, the recommended setting is 12000/6-200 = 1800.