feat(agglayer): add CLAIM and B2AGG cycle count benchmarks#2753
Merged
feat(agglayer): add CLAIM and B2AGG cycle count benchmarks#2753
Conversation
6 tasks
Add benchmarks for CLAIM note (L1/L2 bridge-in) and B2AGG note (bridge-out) consumption alongside existing P2ID benchmarks. - Move shared test vector types and lazy-parsed vectors into miden_agglayer::testing module for reuse across tests and benchmarks - Add benchmark setup functions for CLAIM and B2AGG transactions - Add cycle count assertions for CLAIM note processing (max 64k cycles) Co-Authored-By: partylikeits1983 <partylikeits1983@users.noreply.github.com>
90286c5 to
949890c
Compare
bobbinth
approved these changes
Apr 15, 2026
Contributor
bobbinth
left a comment
There was a problem hiding this comment.
Looks good! Thank you! (not a detailed review - I'm assuming this is mostly just code copy-over).
161cbed to
030bd13
Compare
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.
Turns out that #2618 was never merged into
mainnornext(looking at the commit history, it seems that #2618 was merged intoagglayerbranch short afteragglayergot merged intonext).This is targeting
mainbecause then we can also merge in #2752 cleanly, patch release (it's purely an internal perf change) and have max cycle count lowered back to 128k :)