-
Notifications
You must be signed in to change notification settings - Fork 38
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
perf(levm): benchmark block execution #1859
Draft
dsocolobsky
wants to merge
68
commits into
main
Choose a base branch
from
levm/benchmark_block
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Conversation
This file contains 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
|
|
Benchmark Results ComparisonPR ResultsBenchmark Results: Factorial
Benchmark Results: Factorial - Recursive
Benchmark Results: Fibonacci
Benchmark Results: ManyHashes
Benchmark Results: BubbleSort
Benchmark Results: ERC20 - Transfer
Benchmark Results: ERC20 - Mint
Benchmark Results: ERC20 - Approval
Main ResultsBenchmark Results: Factorial
Benchmark Results: Factorial - Recursive
Benchmark Results: Fibonacci
Benchmark Results: ManyHashes
Benchmark Results: BubbleSort
Benchmark Results: ERC20 - Transfer
Benchmark Results: ERC20 - Mint
Benchmark Results: ERC20 - Approval
|
2e32c92
to
ce16c5d
Compare
8edf075
to
1dd6112
Compare
1dd6112
to
efb08ea
Compare
Oppen
reviewed
Feb 6, 2025
Oppen
reviewed
Feb 6, 2025
5842561
to
6849e42
Compare
5f30865
to
53ceee9
Compare
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.
Motivation
Benchmark the execution of a block in LEVM, to test a more real case scenario.
Description
benchmark_block.rs
which fetches a block via RPC and executes with levm/revm.network/rpc_client
since it's code that I have used in this PR and possibly will be used in other places as well in the future.ExecutionDB
instead of justStore
since I needed this for this PR.Closes #1831
To test
run --package revm_comparison --bin benchmark-block -- --rpc-url SOME_RPC_URL
run --package revm_comparison --bin benchmark-block --features levm -- --rpc-url SOME_RPC_URL
This will use the latest block number, fetched via RPC.
This will take a while and create a cache in a file named
db.bin
, you should take note of the block number and pass it as parameter since in the next run it will use that cached block (and run much faster since it won't download all the data again):run --package revm_comparison --bin benchmark-block -- --rpc-url SOME_RPC_URL --block-number BLOCKNUM
Remember to delete
db.bin
if you want to test again with another block.