-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with sha256 circuit benchmark #5
Comments
Hey @vivijj - can you share what steps you took here so that we can investigate? |
sure, I ran the following script on a Mac Pro M1 with 16GB of RAM: |
I have the same problem |
There is/was a bug in the new witness resolver, and it's fixed in the internal repo, I'll ask to merge it here too. Depending on your machine configuration 1-2-4 kB tests just work (I have 4kB working on M1). It's actually funny because it looks to happen in this test only and doesn't happen in the Era circuits |
Hi,when this issue can be solved, when the internal repo can be published? |
I believe it was updated |
Seems alright. By the way, when do you plan to open source your GPU prover for Boojum? @shamatar |
Closing this issue as resolved. @vivijj we will be opening this repo very soon - I don't think we have an exact date but it is on the list of priorities. |
Hello zkSync Team,
I am currently conducting research using the era-boojum proof system and have encountered an issue during the execution of the SHA-256 benchmark, the program appears to stall at the CSReferenceAssembly::wait_for_witness() function, both run_sha256_prover_non_recursive and run_sha256_prover_recursive_mode_poseidon2.
The text was updated successfully, but these errors were encountered: