Skip to content

Exclude the JAX output stage's compilation from the VMEC++ runtime - #12

Merged
jurasic-pf merged 1 commit into
mainfrom
exclude-jax-compile-from-runtime
Sep 27, 2026
Merged

jurasic-pf merged 1 commit into
mainfrom
exclude-jax-compile-from-runtime

Conversation

@jurasic-pf

Copy link
Copy Markdown
Contributor

Since vmecpp#861, the first vmecpp.run of a process at a given resolution compiles the JAX output stage (about 1 s). The V&V run on vmecpp main then failed the runtime check: dshape took 1.34 s against 0.06 s for VMEC2000 (https://github.com/proximafusion/vmecpp/actions/runs/36309334086/job/108592125248).

run_vmecpp now makes an untimed one-iteration run at the configuration's final radial resolution before the timed run. The compilation depends only on the grid sizes, so this triggers it; the warm-up runtime is written to the run's log. The timed run and the saved wout are unchanged.

Local timings (warm-up / timed): solovev 0.64 s / 0.025 s, cma 0.68 s / 0.25 s, cth_like_fixed_bdy 0.66 s / 0.10 s; a cold solovev run takes 0.63 s. The full suite was not run locally (it needs VMEC2000 in docker).

Since vmecpp#861 the first vmecpp.run of a process at a given resolution
compiles the JAX output stage, about a second: the dshape case then took
1.34 s against 0.06 s for VMEC2000 and failed the runtime check. An
untimed one-iteration run at the final resolution triggers the
compilation before the timed run; its runtime is logged.
@jurasic-pf
jurasic-pf merged commit e49d974 into main Sep 27, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant