-
Notifications
You must be signed in to change notification settings - Fork 879
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
Add CI workflow for performance benchmarks #1983
Conversation
This commit introduces a new GitHub Actions workflow for performance benchmarking. The workflow is triggered on `pull_request_target` events and can be triggered with a "/rerun-benchmarks" comment in the PR. It should be compatible with PRs from both forks and the main repository. It includes steps for setting up the environment, checking out the PR and main branches, installing dependencies, and running benchmarks on both branches. The results are then compared, encoded, and posted as a comment on the PR.
d57e1d6
to
8b1299d
Compare
I might have missed some detail, but how did you fix the permission problem, if you could summarize? This is for my learning purpose. |
Catching up - this looks like a great addition. Since I have been tracking less -- i am going to defer to others for the review and merge. Let me know if you need anything. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So happy you got it working! Added two comments
Using the |
So let's see if this works: /rerun-benchmarks |
Performance benchmarks:
|
It works! Still a bit noisy, but enough to get a general picture. For future improvements we could:
|
commit c0de4a1 Author: Ewout ter Hoeven <E.M.terHoeven@student.tudelft.nl> Date: Sun Jan 21 14:43:08 2024 +0100 Add CI workflow for performance benchmarks (projectmesa#1983) This commit introduces a new GitHub Actions workflow for performance benchmarking. The workflow is triggered on `pull_request_target` events and can be triggered with a "/rerun-benchmarks" comment in the PR. It should be compatible with PRs from both forks and the main repository. It includes steps for setting up the environment, checking out the PR and main branches, installing dependencies, and running benchmarks on both branches. The results are then compared, encoded, and posted as a comment on the PR.
* Make RandomActivationByType.agents_by_type backward compatible * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci * updated warning * Update .gitignore * Update global_benchmark.py * pep8 rename * Update schelling.py * Update schelling.py * Update schelling.py * Update schelling.py * Squashed commit of the following: commit c0de4a1 Author: Ewout ter Hoeven <E.M.terHoeven@student.tudelft.nl> Date: Sun Jan 21 14:43:08 2024 +0100 Add CI workflow for performance benchmarks (#1983) This commit introduces a new GitHub Actions workflow for performance benchmarking. The workflow is triggered on `pull_request_target` events and can be triggered with a "/rerun-benchmarks" comment in the PR. It should be compatible with PRs from both forks and the main repository. It includes steps for setting up the environment, checking out the PR and main branches, installing dependencies, and running benchmarks on both branches. The results are then compared, encoded, and posted as a comment on the PR. * Revert "Squashed commit of the following:" This reverts commit 9485087. * Update .gitignore * further updates * Update benchmarks/WolfSheep/__init__.py --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Note to self: It looks like the comment-triggerd workflows can't find the PR branch correctly. Needs a fix. |
* Make RandomActivationByType.agents_by_type backward compatible * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci * updated warning * Update .gitignore * Update global_benchmark.py * pep8 rename * Update schelling.py * Update schelling.py * Update schelling.py * Update schelling.py * Squashed commit of the following: commit c0de4a1 Author: Ewout ter Hoeven <E.M.terHoeven@student.tudelft.nl> Date: Sun Jan 21 14:43:08 2024 +0100 Add CI workflow for performance benchmarks (#1983) This commit introduces a new GitHub Actions workflow for performance benchmarking. The workflow is triggered on `pull_request_target` events and can be triggered with a "/rerun-benchmarks" comment in the PR. It should be compatible with PRs from both forks and the main repository. It includes steps for setting up the environment, checking out the PR and main branches, installing dependencies, and running benchmarks on both branches. The results are then compared, encoded, and posted as a comment on the PR. * Revert "Squashed commit of the following:" This reverts commit 9485087. * Update .gitignore * further updates * Update benchmarks/WolfSheep/__init__.py * shuffle update * switch to walrus operator in do * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci * revert inplace to False * remove old code --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
This PR introduces a new GitHub Actions workflow for performance benchmarking. The workflow is triggered on
pull_request_target
events and can be triggered with a "/rerun-benchmarks" comment in the PR. It should be compatible with PRs from both forks and the main repository. It includes steps for setting up the environment, checking out the PR and main branches, installing dependencies, and running benchmarks on both branches. The results are then compared, encoded, and posted as a comment on the PR.It's largely based and supersedes #1978 and is reasonably well tested on my own fork in EwoutH#22. It shouldn't need any additional permissions.
The results is a comment on a PR like this:
This PR will start working when it's merged onto the main branch.