ReadingResearchRadarInvestment framework
Sign in / Sign up
← Back to reading
NewsMaterial4 min readDisconfirmAI Editorial

NVIDIA Releases Daviator: Eliminating GPU Bottlenecks in Small-System DFT via k-Point Batching and Mixed Precision

Training machine learning interatomic potentials requires tens of millions to hundreds of millions of density functional theory (DFT) calculations. NVIDIA explains why VASP runs slower on GPUs than CPUs for small systems—due to sequential k-point processing causing kernel launch overhead—and how it systematically addresses this issue through a batched Davidson solver and per-kernel precision analysis workflow.

2026-11-18 23:00 GMT+8

Training next-generation machine learning interatomic potentials (MLIPs) requires tens to hundreds of millions of density functional theory (DFT) calculations as training data. Plane-wave DFT is the gold standard for generating this data, with VASP being its dominant implementation. However, an counter-intuitive phenomenon has long plagued researchers: running small-system DFT calculations on GPUs is actually slower than on CPUs. In a technical blog post released by NVIDIA in November 2026, the root cause of this bottleneck was explained, along with how its new library, Daviator, resolves it through two layers of mechanisms.

The core of the problem lies in the k-point processing mode. The electronic wavefunctions of periodic systems are parameterized by crystal momentum; small unit cells require hundreds to thousands of irreducible k-points to achieve convergence accuracy. Each k-point solve is independent within the Davidson eigensolver step, requiring no inter-k-point communication. However, VASP’s OpenACC GPU port processes k-points sequentially one by one. For large systems, the workload per k-point is sufficient to saturate the GPU; but for small systems paired with dense k-point grids, hundreds of small GPU dispatches per step cause kernel launch overhead to dominate computation time. The article provides a specific case: a single-atom iron system with 752 k-points ran 8 times slower on more expensive GPU hardware than on CPU.

Daviator’s solution replaces sequential loops with batch operations. Its core is a batched Davidson eigensolver that batches FFTs, matrix multiplications, and custom kernels, drastically reducing the number of GPU kernel launches and increasing stream multiprocessor occupancy from partial capacity to near saturation. Data remains resident in GPU memory throughout. VASP retains full control over self-consistent field (SCF) loops, mixing, symmetry, and I/O; Daviator intervenes only at well-defined call boundaries on data already located on the device.

Sign in / Sign up
ReadingResearchRadarInvestment framework

After eliminating the k-point bottleneck, NVIDIA further introduced a mixed-precision execution layer to leverage the asymmetry between FP32 and FP64 throughput in hardware. On data center GPUs, FP64 throughput has remained relatively flat across Hopper, Blackwell, and Rubin architectures, while FP32 throughput continues to grow. Inference-grade and workstation GPUs like the RTX PRO 6000 have an FP32-to-FP64 ratio of 64:1. The issue is that not every kernel in the Davidson pipeline is equally sensitive to precision, and simply comparing FP32 runs against FP64 yields only a binary pass/fail result, failing to reveal where numerical boundaries lie.

The article describes a transferable methodology for analyzing precision requirements. First, the code is instrumented using generic floating-point types with configurable mantissa and exponent bits. Then, run scripts, comparison scripts, and screening scripts are written: for each kernel, the mantissa bits are decremented until the comparison fails, and then the exponent bits are decremented at the minimum available mantissa. This identifies the lowest effective precision for each kernel, determining whether to switch to FP32, improve the implementation to bring it into the FP32 range, or retain it as an FP64 island. NVIDIA points out that true mixed precision requires knowing exactly where the precision boundaries are, because soft failures—energy drift, incorrect convergence, molecular dynamics trajectories that appear valid but actually diverge—are more insidious than hard failures.

Following this workflow, original analysis based on Verificarlo indicated that most of the Davidson algorithm code could run with FP32 arithmetic and storage: FFTs, Hamiltonian application, and orbital updates use FP32, while subspace eigenproblems, tall-skinny matrix multiplications behind subspace matrices, energies, and convergence measures remain in FP64. The remaining FP64 bottleneck is the tall-skinny matrix multiplication in the Rayleigh-Ritz projection; pure FP32 accumulation is insufficient because the output feeds directly into a numerically sensitive eigensolver. NVIDIA resolved this with a split-k algorithm: breaking dot products into FP32 chunks with final accumulation in FP64.

Regarding performance results, NVIDIA reported that Daviator achieved over 2x acceleration relative to the CPU baseline for single-atom iron, a 22x Davidson acceleration for LiFePO4 r2 SCAN functionals, and reduced execution time by over 85% for a 64-atom Bi-doped GaAs system. Mixed precision made the FP32 Davidson solver run 3 to 7 times faster on the RTX PRO 6000, delivering approximately 2x end-to-end acceleration; however, on H100 and H200 GPUs, marginal gains were limited due to FP64 tensor cores matching FP32 throughput. Projections for the OMat24 dataset showed that combining Daviator and mixed precision on the RTX PRO 6000 could reduce costs to about 25% of CPU costs.

It must be clarified that these figures are all self-reported benchmarks from NVIDIA, and the OMat24 projections are extrapolated from 13 representative inputs rather than actual full runs. Currently, Daviator supports only single-node execution; non-collinear spin and pure Gamma-point runs are not yet covered. The convergence limits of mixed precision depend on the input; typically, FP32 can converge to EDIFF thresholds of 10^-4 to 10^-6 eV, and continuing with FP64 is required to break through the FP32 noise floor. This precision analysis methodology itself—instrumentation, per-kernel screening, and FP64 islands—has reference value for other HPC codes needing mixed-precision adaptation, not limited to VASP or the Davidson solver.

Sources

  • developer.nvidia.comNVIDIA Technical Blog↗
Continue researching →