Skip to content

GPU benchmark measured: the unprovable job proves in 34.2s on 32GB Blackwell - #18

Merged
HolyWill90 merged 3 commits into
mainfrom
docs/gpu-measurements
Sep 17, 2026
Merged

HolyWill90 merged 3 commits into
mainfrom
docs/gpu-measurements

Conversation

@HolyWill90

Copy link
Copy Markdown
Owner

Fills the last untested cell of the hardware-class table. Rented an RTX PRO 4500 Blackwell (32 GB VRAM, driver 595.71.05) on vast.ai for under a dollar and ran both benchmarks with VRAM logging:

zkVM cycles CPU prove GPU prove Peak
legacy meta-emulated (524K inst) 168.9M OOM at 32 GB 34.2 s 26.1 GB VRAM
V2 native (524K inst) 1.79M 80.5 s 2.8 s 10.6 GB VRAM
  • SP1 6.8's CUDA prover runs correctly on Blackwell (sm_120) — the architecture question is answered.
  • The 26.1 GB peak explains the 24 GB VRAM floor as the honest minimum for traces of this shape.
  • Outputs byte-identical to every CPU execution; receipts self-verified; V2 receipt 2.8 MB vs legacy 30.6 MB.
  • V2 proving at 2.8 s puts receipt-backed verification inside interactive latency.

Docs-only change (preprint Table 4 + abstract, DESIGN.md GPU section) — CI skipped by the paths filter.

… Blackwell

The last untested cell of the hardware-class table is filled. On an
RTX PRO 4500 Blackwell (32 GB VRAM, driver 595.71.05, rented on
vast.ai for under a dollar):
- legacy meta-emulated job (168.9M zkVM cycles): PROVED in 34.2 s,
  peak 26.1 GB VRAM — the job that OOM-killed the 32 GB CPU host;
- V2 native job (1.79M zkVM cycles): proved in 2.8 s at 10.6 GB peak
  VRAM — a 29x proving speedup over CPU, interactive-latency receipts;
- SP1 6.8's GPU prover runs correctly on Blackwell (sm_120);
- the 26.1 GB peak explains the 24 GB VRAM floor as the honest
  minimum for traces of this shape.

Outputs byte-identical to CPU executions across all runs; receipts
self-verified. Preprint Table 4 and abstract updated; all hardware
envelopes are now measured, nothing projected.
…kipped jobs, which satisfy branch protection

paths-ignore removed the check runs entirely, so branch protection's
required checks never registered and docs-only PRs could not merge at
all (even by admin bypass). Now a 5-second 'changes' job always runs
and every heavy job skips via 'if' when Rust-irrelevant files only
changed (.md, .ipynb, plain docs) — skipped jobs report 'skipped' and
satisfy required-check protection. Workflow files, Rust sources,
manifests, job/ELF artifacts, and arch-tests still trigger the full
suite.
@HolyWill90
HolyWill90 merged commit ede714c into main Sep 17, 2026
11 checks passed
@HolyWill90
HolyWill90 deleted the docs/gpu-measurements branch September 17, 2026 08:20
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