Tackling GPU Bottlenecks in Plane-Wave DFT with K-Point Batching and Mixed Precision NVIDIA introduced Daviator, a library of batched GPU kernels, and a new mixed-precision execution layer for plane-wave DFT in VASP, delivering up to 22x faster time-to-solution and up to 75% lower cost than CPU execution on a projected reference dataset workload. Daviator replaces VASP's sequential per-k-point processing with a batched Davidson eigensolver using batched FFTs, GEMMs and custom kernels, addressing a case where a single-atom iron system with 752 k-points ran 8x slower on more expensive GPU hardware than on CPU. The mixed-precision layer targets inference-class GPUs such as the RTX PRO 6000, which carry a 64:1 FP32:FP64 throughput ratio, as FP64 throughput has held flat across NVIDIA Hopper, Blackwell and Rubin while FP32 throughput keeps rising. Training a next-generation machine learning interatomic potential MLIP requires ground truth: tens to hundreds of millions of density functional theory DFT calculations of energies, forces, and stresses across diverse structures and chemistries. Plane-wave DFT, with VASP as its dominant implementation, is the gold standard for generating that data. It is accurate, well-validated across materials classes, and ubiquitous at the national labs and research institutions running these calculations at scale. As MLIP training datasets have grown, so has the pressure to generate DFT data faster and cheaper. But the small unit cells and dense k-point grids common in MLIP data generation can leave significant GPU performance unused. VASP’s OpenACC implementation has delivered meaningful speedups, especially for large-system calculations. However, for smaller systems, sequential k-point processing limits GPU utilization. At the same time, AI workloads are reshaping GPU hardware development toward lower-precision data types, creating a growing gap between what modern NVIDIA GPUs can deliver and what FP64-only HPC codes are optimized for. This post introduces two new NVIDIA capabilities that address these bottlenecks. The first, Daviator, resolves the small-system GPU performance problem through k-point and spin-batched GPU kernels. In particular, a batched Davidson solver delivers significant performance gains. The second, a new mixed precision execution layer, enables further performance gains, especially on inference-class GPUs with a high FP32:FP64 throughput ratio. For a projected reference dataset workload, the results show up to 22x faster time-to-solution and up to 75% lower cost compared to CPU execution, depending on hardware and configuration. The GPU bottleneck in plane-wave DFT In periodic systems, electronic wavefunctions are parameterized by crystal momentum, a discrete set of k-points that samples the Brillouin zone. For periodic structures with small unit cells, hundreds to thousands of irreducible k-points are required to achieve well-converged results. Each k-point solve is largely independent; for instance, no inter-k-point communication is required during the Davidson eigensolver step. Despite this independence, VASP’s OpenACC GPU port processes k-points sequentially. For large systems, the work per k-point can fully saturate a GPU, but for small systems with dense k-point grids, the hundreds of small GPU dispatches per step causes kernel launch overhead to dominate compute time. The result: a single-atom iron system with 752 k-points ran 8x slower on the more expensive GPU hardware than on CPU. Thus, researchers working at this scale were left with a manual routing decision based on the size of the job. Additionally, plane-wave DFT traditionally runs in FP64, a conservative default that guarantees accuracy throughout the solver pipeline. But GPU hardware is no longer symmetric in this regard. On data center GPUs, FP64 throughput has held flat across NVIDIA Hopper, Blackwell, and Rubin GPUs, while FP32 throughput has continued to increase. Inference-class and workstation GPUs like the RTX PRO 6000 push this further, with a 64:1 FP32:FP64 ratio Figure 1 . As AI workloads drive hardware development toward lower-precision data types, the fraction of peak GPU throughput available to FP64-only codes is stagnating. Daviator: Batching k-points for GPU saturation Daviator is a library of GPU kernels developed by NVIDIA that replaces sequential per-k-point processing in plane-wave DFT inner loops with batched GPU operations. At the core of the transformation lies a batched Davidson eigensolver that replaces sequential loops that cause latency with batched FFTs, GEMMs, and custom kernels. This drops the number of GPU kernel launches drastically, enabling SM occupancy to go from a fraction of capacity to near saturation. Data stays resident in GPU memory throughout. VASP retains full ownership of the SCF loop, mixing, symmetry, and I/O; Daviator integrates at well-defined call boundaries over data already on device. Running a calculation Daviator will be available through the NVIDIA ALCHEMI VASP microservice by setting LDAVIATOR=True in the INCAR. Existing VASP inputs work without modification. The POSCAR, INCAR, and KPOINTS below are a standard setup for a k-point-dense metallic system. Daviator intercepts the Davidson solver internally ALGO = Normal and routes it through batched GPU operations. POSCAR: Fe1 1.0 2.3017038599999999 0.0000000000000000 -0.8137751999999999 -1.1508519300000000 1.9933340200000000 -0.8137751999999999 0.0000000000000000 0.0000000000000000 2.4413256099999998 Fe 1 direct 0.0000000000000000 0.0000000000000000 0.0000000000000000 Fe INCAR: ALGO = Normal LDAVIATOR = True EDIFF = 5e-05 IBRION = 2 ISIF = 3 ISMEAR = 1 ISPIN = 2 NBANDS = 12 NSIM = 6 LASPH = True LMAXMIX = 4 LORBIT = 11 LREAL = False LWAVE = False MAGMOM = 1 5.0 NELM = 100 NSW = 3 PREC = Accurate SIGMA = 0.05 KPAR = 1 KPOINTS: Gamma-centred 30x30x30 mesh 0 Gamma 30 30 30 Some of Daviator’s GPU kernels are specialized for the batch sizes they meet and may trigger a compilation on first use. Add these lines to your job script before launching VASP to ensure efficient caching: export CUDA CACHE PATH=/tmp/cudacache fast storage, not $HOME export CUDA CACHE DISABLE=0 make sure caching is on Finally, run as usual: mpirun -np 1 vasp std For now, VASP with Daviator is limited to single-node execution. Multi-node support, coverage of systems with non-collinear spins vasp ncl and explicit gamma-only runs vasp gam is expected to be released at a later stage. Results The benchmarks below compare Daviator against VASP 6.6.0 CPU and OpenACC baselines on NVIDIA H100s/H200s and B200s. Daviator overcomes the OpenACC port’s limitations; a single iron atom achieves over 2x speed-ups relative to the CPU baseline Figure 2 . The gains increase for higher-accuracy functionals: the 22x Davidson speedup on LiFePO