Skip to content

perf: increase preallocation vpmm size for halo2 - #621

Draft
Aalanli wants to merge 14 commits into
develop-v2.0.0-rc.2from
inc_vpmm
Draft

perf: increase preallocation vpmm size for halo2#621
Aalanli wants to merge 14 commits into
develop-v2.0.0-rc.2from
inc_vpmm

Conversation

@Aalanli

@Aalanli Aalanli commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

Increases vpmm preallocation to get rid of first run warmup and page faults in halo2 prover. This makes the benchmark more representative of real-world use cases.

Default 16GB prealloc:
image

TODO: updated profile of 25 GB prealloc.

Qumeric and others added 14 commits May 16, 2026 11:13
* feat: enable cached root prover benchmark

* fix: root prover bench after sdk suggestions

* feat: add prove root benchmark to actions

* fix: address comments

* fix: add separate proof cache dir

* fix: add separate proof cache dir

* fix: update deps

---------

Co-authored-by: Allan Lin <allanl@intrinsictech.xyz>
…rk CI

sccache, cargo fingerprints, and host_cache_key all key on the literal
RUSTFLAGS string, so with -Ctarget-cpu=native, artifacts built on one EC2
instance family are cache hits on another despite different machine code,
causing SIGILL (e.g. AVX-512 code from g7e reused on g6e/Zen 3).

Resolve "native" to the explicit host CPU name (e.g. znver3) before setting
RUSTFLAGS, so the CPU identity flows into all three cache keys. Falls back
to "native" if rustc cannot name the host CPU.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The nightly toolchain was hardcoded in 5 places across the reth benchmark
workflow and run.sh. Read the channel from rust-toolchain.toml instead so
toolchain bumps only touch one file.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
g6e capacity has been limited; g7e is more available.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@shuklaayush
shuklaayush force-pushed the develop-v2.0.0-rc.2 branch from f2e1f54 to 0e19ad8 Compare June 19, 2026 20:07
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.

5 participants