MVP gnark GPU acceleration
@wwared is already working on this.
Since Jun 12, 2024.
Assessment
This issue has not been assessed yet.
Description
We want to:
- accelerate the final gnark proof using the GPU + Ingonyama's Icicle,
- benchmark the speedups,
- integrate the choice of hardware, deployment instructions in the release package.
This would be guesstimated to reduce our e2e proof time by -5min.
- Dominant language
- Rust
- Stars
- 80
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from argumentcomputer/sphinx
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
argumentcomputer/sphinx#206 ·
-
The termination check is under-constrained due to incomplete check of "public_values.next_pc == 0". Open
Difficulty 3/5 1-2 days Newbie friendliness 72/100
argumentcomputer/sphinx#205 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
argumentcomputer/sphinx#204 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
argumentcomputer/sphinx#188 ·
-
SHA-512 improvements Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
argumentcomputer/sphinx#181 ·
All issues in argumentcomputer/sphinx
Similar issues
-
todo:perf
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
ACP agents get no MCP servers when the thread is created before the project's first worktree loads Openstate:needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
zed-industries/zed#64611 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ontola/atomic-server#1625 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
objectionary/phie#154 ·