Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: add full record of visited_pcs to support starknet-replay #2

Closed
wants to merge 5 commits into from

Conversation

Eagle941
Copy link
Collaborator

@Eagle941 Eagle941 commented Aug 6, 2024

Added feature full_visited_pcs to record the full vector of visited pcs instead of just the HashSet in CachedState

@Eagle941 Eagle941 changed the title Added full record of visited_pcs to support starknet-replay chore: ADD full record of visited_pcs to support starknet-replay Aug 7, 2024
@Eagle941 Eagle941 changed the title chore: ADD full record of visited_pcs to support starknet-replay chore: add full record of visited_pcs to support starknet-replay Aug 7, 2024
Copy link

@iamrecursion iamrecursion left a comment

Choose a reason for hiding this comment

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

At first look this seems reasonable, barring the name for the feature. Have you run benchmarking to ensure that nothing has changed in terms of performance without your new feature enabled? We need to ensure that this does not introduce any performance regressions to the non-feature-enabled use-case, and it seemed to me like some code has indeed changed in those paths.

crates/blockifier/Cargo.toml Outdated Show resolved Hide resolved
crates/blockifier/src/lib.rs Outdated Show resolved Hide resolved
`vector_of_visited_program_counters`.
`blockifier/transaction_executor.rs`.
@Eagle941 Eagle941 marked this pull request as draft August 31, 2024 00:47
@Eagle941 Eagle941 closed this Sep 17, 2024
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