You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been building a demo around SP1 and testing full proving to bench on two separate machines that exhibit the same behavior: RAM is saturated and swap is then saturated.
See above for basic system specs, notably 32 GB RAM + 20 GB swap.
Reproduce
With SP1 installed:
# open some system monitor like btm or top
git clone https://github.com/nuke-web3/sp1-chacha.git
cd sp1-chacha
cargo r -r -- --prove
# BE SURE TO WATCH RAM & SWAP USE!
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Component
Other (please describe)
Have you ensured that all of these are up to date?
What version of SP1 SDK are you on?
sp1-zkvm = "4.0.0"
What version of the cargo prove CLI are you on?
cargo-prove sp1 (a80c17c 2025-04-01T00:41:38.259051986Z)
cargo 1.86.0 (adf9b6ad1 2025-02-28)
Operating System
None
Describe the bug
I have been building a demo around SP1 and testing full proving to bench on two separate machines that exhibit the same behavior: RAM is saturated and swap is then saturated.
For details, see nuke-web3/sp1-chacha#1
Example behavior monitored by
btm
See above for basic system specs, notably 32 GB RAM + 20 GB swap.
Reproduce
With SP1 installed:
The text was updated successfully, but these errors were encountered: