LASYNC: Difference between revisions
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
If {{TAG|LASYNC}}=''.TRUE.'' is set in the INCAR file, VASP will try to overlap communication with calculations. This switch is only supported in VASP.4.5 and newer releases, its use is however not recommended, since {{TAG|LASYNC}}=''.TRUE.'' has not been tested carefully. | If {{TAG|LASYNC}}=''.TRUE.'' is set in the INCAR file, VASP will try to overlap communication with calculations. This switch is only supported in VASP.4.5 and newer releases, its use is however not recommended, since {{TAG|LASYNC}}=''.TRUE.'' has not been tested carefully. | ||
Overlapping communication and calculations, might improve performance a little bit, but it is also possible that the performance drops significantly. Please try yourself | Overlapping communication and calculations, might improve performance a little bit, but it is also possible that the performance drops significantly. Please try yourself. | ||
{{sc|LASYNC|Examples|Examples that use this tag}} | {{sc|LASYNC|Examples|Examples that use this tag}} | ||
Revision as of 07:44, 19 July 2022
LASYNC = [logical]
Default: LASYNC = .FALSE.
Description: This tag controls the overlap in communication.
If LASYNC=.TRUE. is set in the INCAR file, VASP will try to overlap communication with calculations. This switch is only supported in VASP.4.5 and newer releases, its use is however not recommended, since LASYNC=.TRUE. has not been tested carefully.
Overlapping communication and calculations, might improve performance a little bit, but it is also possible that the performance drops significantly. Please try yourself.