timing and accounting information
Posted: Mon Mar 28, 2022 1:10 pm
Dear Vasp community,
At the end of each vasp job, the timing and accounting information is printed in the OUTCAR. However, I cannot make any sense of the maximum memory used stated there. I never checked for DFT calculations as memory is usually not a bottleneck there, but I was interested in the values in regard with RPA calculations. The value stated did not seem to make any sense at all. As comparison, I used sacct to retrieve the MaxRSS value from the submission system. This value DID make sense, but could not correlate in any way with the maximum memory stated in the OUTCAR. I give here a few examples (all calculations were run on 128cpus):
max_mem_from_OUTCAR MaxRSS
calc1 1052332 kb 465217 K
calc2 1684456 kb 1512909 K
calc3 1831260 kb 1690932 K
calc4 2680032 kb 2054935 K
Is this a bug or a feature that I do not understand?
Thank you and best regards,
Katharina
At the end of each vasp job, the timing and accounting information is printed in the OUTCAR. However, I cannot make any sense of the maximum memory used stated there. I never checked for DFT calculations as memory is usually not a bottleneck there, but I was interested in the values in regard with RPA calculations. The value stated did not seem to make any sense at all. As comparison, I used sacct to retrieve the MaxRSS value from the submission system. This value DID make sense, but could not correlate in any way with the maximum memory stated in the OUTCAR. I give here a few examples (all calculations were run on 128cpus):
max_mem_from_OUTCAR MaxRSS
calc1 1052332 kb 465217 K
calc2 1684456 kb 1512909 K
calc3 1831260 kb 1690932 K
calc4 2680032 kb 2054935 K
Is this a bug or a feature that I do not understand?
Thank you and best regards,
Katharina