Repository navigation
Conversation
The zero fetcher built an HTTP session and a solver group for every query, even with RPC disabled and zero solver workers. CREATE now queries unknown destination accounts, so contract-creation benchmarks repeated this setup thousands of times and timed out. On macOS, TLS initialization spawns security to read certificates, leaving the benchmark waiting for local subprocesses despite making no RPC calls. Remove zero and migrate its concrete callers to noRpcConcreteFetcher. Add concreteOracle for concrete runs that can fetch RPC state. Both share dispatch with oracle; a typed SMT handler makes solver access unreachable for concrete queries while symbolic queries use the caller's existing SolverGroup. This keeps account, storage, FFI and environment behavior in one place without per-query resource setup. Use the concrete fetcher for CLI execution, test setup and counterexample replay, removing the zero-worker solver group from exec. Make sessions optional through the CLI and unit-test options and create them only when RPC is configured. Equivalence checking also skips its unused session. RPC runs retain shared sessions and caches, and symbolic runs retain their caller-owned solver groups.
elopez
force-pushed
the
perf-contract-mk
branch
from
November 14, 2026 02:46
727d68c to
522039e
Compare
Collaborator
Author
|
Some nice results in contractCreationMem and a bit better in contractCreation as well bench-perf results |
elopez
force-pushed
the
perf-contract-mk
branch
2 times, most recently
from
November 14, 2026 03:04
a799d41 to
8f0f99a
Compare
Replace the accumulated monadic action chain (m >> write >> write >> ...) with direct ST writes during ByteString iteration. The old approach created O(n) closures for the >> chain; the new approach writes directly to the mutable vector with zero closure allocation.
elopez
force-pushed
the
perf-contract-mk
branch
from
November 14, 2026 03:46
8f0f99a to
cf2995b
Compare
elopez
marked this pull request as ready for review
November 14, 2026 03:46
Collaborator
Author
|
(first commit is #1261 ) |
3 of 8 tasks
Collaborator
|
#1261 is now merged, this can be rebased. |
This branch has not been deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Replace the accumulated monadic action chain (m >> write >> write >> ...)
with direct ST writes during ByteString iteration. The old approach
created O(n) closures for the >> chain; the new approach writes directly
to the mutable vector with zero closure allocation.
Checklist