Skip to content

Add tx-trace-snapshot producer#2794

Open
Al-Kindi-0 wants to merge 2 commits intonextfrom
al/tx-trace-snapshot
Open

Add tx-trace-snapshot producer#2794
Al-Kindi-0 wants to merge 2 commits intonextfrom
al/tx-trace-snapshot

Conversation

@Al-Kindi-0
Copy link
Copy Markdown
Collaborator

Adds a new bin target under bin/bench-transaction/src/bin/tx-trace-snapshot.rs that executes representative transaction contexts through the VM, builds a real ExecutionTrace, reads per-component trace lengths from TraceLenSummary, and writes one JSON snapshot per scenario under bin/bench-transaction/snapshots/. These snapshots are the input to miden-vm's new miden-synthetic-tx-kernel bench.

This is a simplified variant of the cross-repo benchmark approach originally prototyped in #2391. Rather than maintaining a fused bench that runs miden-vm code from within this repo, this producer only writes a small JSON descriptor of the workload; the bench itself lives entirely in miden-vm and has no runtime dependency on protocol.

Add a changelog entry for the tx trace snapshot producer and cover the committed snapshots with schema, source, version, row-count, chiplet-sum, and padded-bracket assertions.

Also document that the VM consumer hard-matches padded core-side and chiplet brackets while treating per-chiplet shape as advisory profiling metadata, and leave an explicit ACE accessor TODO for the producer.
Copy link
Copy Markdown
Contributor

@huitseeker huitseeker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you so much! I just added a commit that adds tests and docs which make the trace snapshots harder to break: they now check the schema, row totals, and padded trace sizes that the VM benchmark relies on.

@huitseeker huitseeker marked this pull request as ready for review April 23, 2026 14:29
@huitseeker huitseeker requested a review from adr1anh April 23, 2026 14:29
@huitseeker huitseeker requested a review from bobbinth April 24, 2026 10:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants