LASYNC: Difference between revisions
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
Description: Controls the overlap in communication. | Description: Controls the overlap in communication. | ||
---- | ---- | ||
If {{TAG|LASYNC}}=''.TRUE.'' is set in the INCAR file, VASP will try to overlap communication with calculations. This | If {{TAG|LASYNC}}=''.TRUE.'' is set in the INCAR file, VASP will try to overlap communication with calculations. | ||
This might improve performance or degrade it depending on the MPI library and hardware you are running on. | |||
Please do your own testing and compare the runtimes and results before using this tag in production runs. | |||
Compiling VASP using the [[Precompiler_options#-DPROFILING|-DPROFILING]] precompiler switch provides a detailed timing of the different VASP routines which helps in determining if there is a performance gain. | |||
Please report any issues in the [https://www.vasp.at/forum/ VASP forum]. | |||
{{sc|LASYNC|Examples|Examples that use this tag}} | {{sc|LASYNC|Examples|Examples that use this tag}} | ||
Latest revision as of 08:12, 19 July 2022
LASYNC = [logical]
Default: LASYNC = .FALSE.
Description: Controls the overlap in communication.
If LASYNC=.TRUE. is set in the INCAR file, VASP will try to overlap communication with calculations. This might improve performance or degrade it depending on the MPI library and hardware you are running on. Please do your own testing and compare the runtimes and results before using this tag in production runs. Compiling VASP using the -DPROFILING precompiler switch provides a detailed timing of the different VASP routines which helps in determining if there is a performance gain. Please report any issues in the VASP forum.