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
While we are still reliant on barretenberg.wasm for blackbox functions, we can use the barretenberg.wasm file to compute these blackbox functions. It allows us to not need to compile barretenberg from source. It is pretty slow to compile in wasmer and slow in general.
Solution
We can reduce compile times by only including the necessary components in the .wasm file for blackbox functions. This reduces the compile times from 15seconds to zero on compilers like LLVM and cranelift (not sure why it takes so long) -- you can verify this using Wasmer.
The text was updated successfully, but these errors were encountered:
resolves#1823
# Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if
the PR is ready to merge.
- [ ] If the pull request requires a cryptography review (e.g.
cryptographic algorithm implementations) I have added the 'crypto' tag.
- [ ] I have reviewed my diff in github, line by line and removed
unexpected formatting changes, testing logs, or commented-out code.
- [ ] Every change is related to the PR description.
- [ ] I have
[linked](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue)
this pull request to relevant issues (if any exist).
Problem
While we are still reliant on barretenberg.wasm for blackbox functions, we can use the barretenberg.wasm file to compute these blackbox functions. It allows us to not need to compile barretenberg from source. It is pretty slow to compile in wasmer and slow in general.
Solution
We can reduce compile times by only including the necessary components in the .wasm file for blackbox functions. This reduces the compile times from 15seconds to zero on compilers like LLVM and cranelift (not sure why it takes so long) -- you can verify this using Wasmer.
The text was updated successfully, but these errors were encountered: