-
Notifications
You must be signed in to change notification settings - Fork 177
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
Implement resource usage report #249
Comments
Thank you for the request. We are definitely considering adding transactions profiling at some point. |
This should be considered as well on cairo level - which could enable users to assert gas consumed from a test. Also i think we should profile on transaction level and as well sum the transactions gas for a whole test (if a person wants to know the whole flows' cost) |
Blocked by #327 |
We could start by implementing it for a single test case as a whole as it will be the simplest. Later we could try to do it on a transaction level maybe something like this
|
Wouldn't it be better to have step counts rather than gas usage? |
@enitrat Sure but steps are only part of the picture as builtins can impose significant cost as well. Ideally we should report:
|
yes, indeed, I just wanted to make sure we were not talking about Sierra Gas (I'm still not sure it's actually mapped to "real" execution resources) |
#362 Should be taken under consideration |
Related: #462 |
Blocked by #547 |
<!-- Reference any GitHub issues resolved by this PR --> Closes #249 Closes #362 ## Introduced changes <!-- A brief description of the changes --> - added gas estimation ## Breaking changes <!-- List of all breaking changes, if applicable --> - `call_contract`, `deploy`, and `deploy_at` Cheatnet API changed ## Checklist <!-- Make sure all of these are complete --> - [x] Linked relevant issue - [ ] Updated relevant documentation - [x] Added relevant tests - [x] Performed self-review of the code - [ ] Added changes to `CHANGELOG.md` --------- Co-authored-by: Arcticae <tomekgsd@gmail.com>
To what component is your bug related to?
Forge
Feature Request
Using the Blockifier, we can get the resource used for
invoke
transaction invocations.Would be great to have a flag
--resource-report
to print out resources used (steps, built-ins etc)The text was updated successfully, but these errors were encountered: