GMX-NONBONDED-BENCHMARK(1)

📦
version 2026.4 · 8 versions
, in nixpkgs unstable, ubuntu stonking

✨ NAME ✨

gmx-nonbonded-benchmark — a benchmarking tool for the non-bonded pair kernels. it's giving "I stress-test your CPU so you don't have to" 💅

🦋 SYNOPSIS 🦋

gmx nonbonded-benchmark [-o [<.csv>]] [-size <int>] [-nt <int>]
             [-simd <enum>] [-coulomb <enum>]
             [-interactmodifier <enum>] [-[no]table]
             [-combrule <enum>] [-[no]halflj] [-[no]energy]
             [-[no]all] [-cutoff <real>] [-iter <int>]
             [-warmup <int>] [-[no]cycles] [-[no]time]

🌸 DESCRIPTION 🌸

okay bestie, sit down, because gmx nonbonded-benchmark is lowkey the main character of performance testing. she runs benchmarks for one or more of the so-called Nbnxm non-bonded pair kernels. ✨

and why do we care?? because the non-bonded pair kernels are the most compute intensive part of MD simulations and usually comprise 60 to 90 percent of the runtime. yeah. that much. 😭 so obviously they're highly optimized, and there are several different setups available to compute the same physical interactions. plus there are different physical treatments of Coulomb interactions, and optimizations for atoms that don't have Lennard-Jones interactions. 🫶

there are also different physical treatments of Lennard-Jones interactions, but ngl only a plain cut-off is supported in this tool, because that is by far the most common treatment. and finally — while force output is always necessary, energy output is only required at certain steps. and when you add it all up? there are 36 relevant combinations of options. and the combinations double to 72 when two different SIMD setups are supported. 🤯 you can run all of these with a single invocation using the -all option. iconic behavior, honestly.

the behavior of each kernel is affected by caching behavior, which is determined by the hardware used together with the system size and the cut-off radius. the larger the number of atoms per thread, the more L1 cache is needed to avoid L1 cache misses. the cut-off radius mainly affects the data reuse: a larger cut-off results in more data reuse and makes the kernel less sensitive to cache misses. ✨

OpenMP parallelization is used to utilize multiple hardware threads within a compute node. in these benchmarks there is no interaction between threads, apart from starting and closing a single OpenMP parallel region per iteration. additionally, threads interact through sharing and evicting data from shared caches. the number of threads to use is set with the -nt option. thread affinity is important — especially with SMT and shared caches. affinities can be set through the OpenMP library using the GOMP_CPU_AFFINITY environment variable. 👑

the benchmark tool times one or more kernels by running them repeatedly for a number of iterations set by the -iter option. an initial kernel call is done to avoid additional initial cache misses (warmup is real and it matters, bestie 🧚). times are recording in cycles read from efficient, high accuracy counters in the CPU. note that these often do not correspond to actual clock cycles. 💀 for each kernel, the tool reports the total number of cycles, cycles per iteration, and (total and useful) pair interactions per cycle.

because a cluster pair list is used instead of an atom pair list, interactions are also computed for some atom pairs that are beyond the cut-off distance. these pairs are not useful (except for additional buffering, but that is not of interest here), only a side effect of the cluster-pair setup. the SIMD 2xMM kernel has a higher useful pair ratio then the 4xM kernel due to a smaller cluster size, but a lower total pair throughput.

🚨 bestie listen. it is best to run this — or, for that matter, any — benchmark with locked CPU clocks, because thermal throttling can significantly affect performance. if that is not an option, the -warmup option can be used to run initial, untimed iterations to warm up the processor. 🔥

the most relevant regime is between 0.1 to 1 millisecond per iteration. thus it is useful to run with system sizes that cover both ends of this regime. 🌈

the -simd and -table options select different implementations to compute the same physics. the choice of these options should ideally be optimized for the target hardware. historically, we only found tabulated Ewald correction to be useful on 2-wide SIMD or 4-wide SIMD without FMA support. as all modern architectures are wider and support FMA, we do not use tables by default. the only exceptions are kernels without SIMD, which only support tables. 🌸

options -coulomb, -combrule, -interactmodifier and -halflj depend on the force field and composition of the simulated system. the optimization of computing Lennard-Jones interactions for only half of the atoms in a cluster is useful for water, which does not use Lennard-Jones on hydrogen atoms in most water models. in the MD engine, any clusters where at most half of the atoms have LJ interactions will automatically use this kernel. 💧 and finally, the -energy option selects the computation of energies, which are usually only needed infrequently. periodt.

💖 OPTIONS 💖

🎀 Options to specify output files

  • -o [<.csv>] (nonbonded-benchmark.csv) (Optional) — also output results in csv format 📄 so you can spreadsheet-ify your flex.

💅 Other options

  • -size <int> (1) — the system size is 3000 atoms times this value. math is math, bestie 🧮
  • -nt <int> (1) — the number of OpenMP threads to use 🧵
  • -simd <enum> (auto) — SIMD type. auto runs all supported SIMD setups, or no SIMD when SIMD is not supported: auto, no, 4xm, 2xmm ⚡
  • -coulomb <enum> (ewald) — the functional form for the Coulomb interactions: ewald, reaction-field ⚛️
  • -interactmodifier <enum> (PotShift) — the Coulomb / VdW interaction modifier. reported under the 'intmod.' column: PotShift, PotSwitch, ForceSwitch 🪄
  • -[no]table (no) — use lookup table for Ewald correction instead of analytical 📊
  • -combrule <enum> (geometric) — the LJ combination rule. reported under the 'comb.' column: geometric, lb, none 🧬
  • -[no]halflj (no) — use optimization for LJ on half of the atoms. reported under the 'LJ' column 🍓
  • -[no]energy (no) — compute energies in addition to forces 🔋
  • -[no]all (no) — run all 36 combinations of options for coulomb, halflj, combrule, interactmodifier. go big or go home 💥
  • -cutoff <real> (1) — pair-list and interaction cut-off distance ✂️
  • -iter <int> (100) — the number of iterations for each kernel 🔁
  • -warmup <int> (0) — the number of iterations for initial warmup ☕
  • -[no]cycles (no) — report cycles/pair instead of pairs/cycle 🔄
  • -[no]time (no) — report micro-seconds instead of cycles ⏱️

👀 SEE ALSO 👀

more information about GROMACS is available at http://www.gromacs.org/. go read, iykyk 🦋

2026, GROMACS development team 💜

and that's the whole thing, bestie!! you just read the entire gmx-nonbonded-benchmark(1) page and honestly? slay. this was GROMACS 2026.4, dated Oct 02, 2026 — go lock your CPU clocks, warm up your processor, and benchmark like the main character you are. mwah 💅✨🎀🫶

📦 where this page comes from