More efficient provers loading #708
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
binier
force-pushed
the
feat/node/web
branch
11 times, most recently
from
25aab6f to
2970e3e
Compare
…he main thread and reuse it for `P2pTaskRemoteSpawner` re: #659
…edger reconstruction to restart
binier
force-pushed
the
feat/node/web
branch
from
cc84cb1 to
65ae798
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Avoid constructing provers for things we don't need. E.g. if we aren't running a snark worker, we don't need transaction prover. Or if we aren't running block producer we don't block prover. For zkapp provers, we don't need them yet as there is no way to create zkapp from openmina.