-
Notifications
You must be signed in to change notification settings - Fork 595
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
Comment output of cachegrind in PR #797
Comments
Can i help out with this issue? Seems simple enough as an entrypoint for someone who's new to the EVM ecosystem. |
Go for it, it is mostly github actions and how to output it in PR (not sure what github plugging are out there for it) |
@rakita A bit confused as to what needs to be done. Do you mind giving me a bit of context? I reassure you, this would get lesser and lesser with the next few contributions. If you wish, I can ping you somewhere else too (a discord server, the revm telegram group etc) |
Idea is to run valgrind cachegrind on every new PR. cachegrind is used to deduce the number of executed instructions and is a good metric to check how fast/slow the program is. In comparison, time measurement can be variable and hard to get one value, while num of the instruction is always the same for the same program so it is a good ballpark. So executing this on every PR means adding github action: https://github.com/bluealloy/revm/tree/main/.github/workflows and using some (i hope it exists) github plugin that outputs this to the PR as a comment. Hope that this makes it clearer. |
Thanks! That does. Let me play around with this and come up with a draft. |
* ci: adding cachegrind to PRs! * ci: making it trigger everytime a PR opens and a comment is made * ci: simplifying run rules * ci: making it work * ci: triggering again to see * ci: fixing arguments * ci: installing valgrind * ci: installing cg_annotate * ci: playing around a bit more * ci: this should get the first working comment * ci: this should get the first working comment (1) * ci: this should get the first working comment (2 :P) * ci: this should get the first working comment (3 :P) * ci: trying again lol * ci: trying again lol * ci: trying again lol * ci: trying again lol * ci: trying again lol * ci: trying again lol * ci: debugging * ci: debugging * ci: debugging * ci: debugging * ci: debugging * ci: debugging * ci: debugging * ci: debugging * ci: debugging * ci: debugging * ci: debugging * ci: debugging * ci: debugging * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: sigh * ci: removing garbage * ci: adding edit last flag * ci: testing around with no previous comment edge case * ci: testing with permissions * ci: giving workflow further more permissions * ci: testing workflow
Still need to fix PAT and github token but issue is considered done |
Not sure how to do this but would be very beneficial
As i am on mac valgrind does not work and i have a Docker file:
Run docker with:
docker run -it -v $PWD:/tmp -w /tmp valgrind:1.0
And I run snailtracer to get results like this:
The text was updated successfully, but these errors were encountered: