execution: reduce allocations in EIP-7906 assertion views
Maintainers usually reply within 1 day
@yperbasis is already working on this.
Since Nov 16, 2026.
Assessment
This issue has not been assessed yet.
Description
Follow-up to #25602.
FrameContext.TransactionTrace caches its result, but its first use builds all change tables and event indexes. It calls LogsSince, which deep-copies log data already copied for frame receipts. A storage-only assertion therefore also pays for log copies and event indexing.
Worthwhile optimizations:
- Reuse stable log data during the read-only POST_TX suffix instead of copying payloads again. Make ownership and lifetime explicit; coordinate with the receipt log ownership work in #25738.
- Build event views and their address/topic indexes only when requested, retaining the per-transaction cache. Measure the benefit before extending lazy construction to other tables.
Local synthetic benchmarks at 36d19eaabf55f4eff36029a4ffcbc7fa853084ce, using Go 1.26.8 on an Apple M2 Max, measured these total allocations per first view construction:
| Input | Bytes allocated | Allocations |
|---|---|---|
| 1,000 changed storage slots, no logs | 431,968 | 54 |
| 1,000 logs with 1 KiB of data and two topics each, no state changes | 1,573,856 | 1,046 |
| Reuse an already-built view | 0 | 0 |
The setup was outside the timed loop; each construction run cleared only the cached view. These figures include all view construction, not just log copying. CPU timings were too noisy to support a throughput claim.
Compare allocations and time for storage-only assertions, log-heavy assertions and repeated queries. Preserve event order, topic deduplication, transaction boundaries and rollback behavior. Borrowed data must not escape its valid lifetime or change receipt/tracer output. Keep ordinary transaction storage paths allocation-free and check them with the existing access-list and SLOAD/SSTORE benchmarks.
- Dominant language
- Go
- Stars
- 3.6k
- Forks
- 1.6k
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 820
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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 erigontech/erigon
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
erigontech/erigon#26523 ·
Maintainers usually reply within 1 day
-
flaky test
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
erigontech/erigon#26230 ·
Maintainers usually reply within 1 day
-
txnprovider/txpool: pending nonce counts past gaps in the poolPossibly taken @yperbasis claimed this 7 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
erigontech/erigon#26014 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
tracing: expose custom error selector and raw payload in callTracer revertReasonPossibly taken @lupin012 claimed this 9 days ago. OpenRPC
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
erigontech/erigon#25928 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
txnprovider/txpool: remove redundant blob/commitment length checkPossibly taken @yperbasis claimed this 14 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
erigontech/erigon#25432 ·
Maintainers usually reply within 1 day
All issues in erigontech/erigon
Similar issues
-
enhancement exporter/awskinesis needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
open-telemetry/opentelemetry-collector-contrib#53334 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
SocialGouv/iterion#3376 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
seaweedfs/seaweedfs#12740 · 2 comments ·
Maintainers usually reply within 1 day
-
area:indexer bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
seanb4t/codegraph-go#385 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day