KPAR: Difference between revisions
No edit summary |
No edit summary |
||
| Line 24: | Line 24: | ||
{{sc|KPAR|Examples|Examples that use this tag}} | {{sc|KPAR|Examples|Examples that use this tag}} | ||
---- | ---- | ||
[[Category:INCAR]][[Category:Performance]][[Category:parallelization]] | [[Category:INCAR]][[Category:Performance]][[Category:parallelization]] | ||
Revision as of 17:48, 11 March 2019
KPAR = [integer]
Default: KPAR = 1
Description: KPAR determines the number of k-points that are to be treated in parallel (available as of VASP.5.3.2).
VASP currently offers parallelization and data distribution over bands and/or over plane wave coefficients (see NCORE and NPAR), and as of VASP.5.3.2, parallelization over k-points. To obtain high efficiency on massively parallel systems or modern multi-core machines, it is strongly recommended to use all at the same time. Most algorithms work with any data distribution (except for the single band conjugated gradient, which is considered to be obsolete).
The set of k-points is distributed over KPAR groups of compute cores, in a round-robin fashion. This means that a group of N=(# of cores/KPAR) compute cores together work on an individual k-point (choose KPAR such that it is an integer divisor of the total number of cores). Within this group of N cores that share the work on an individual k-point, the usual parallelism over bands and/or plane wave coefficients applies (as set by means of the NCORE and NPAR tags).
Note: the data is not distributed additionally over k-points.
Related Tags and Sections
NCORE, NPAR, LPLANE, LSCALU, NSIM, LSCALAPACK, LSCAAWARE