Add CodSpeed performance benchmarks and CI workflow#62
Open
codspeed-hq[bot] wants to merge 1 commit into
Open
Conversation
Author
Congrats! CodSpeed is installed 🎉
You will start to see performance impacts in the reports once the benchmarks are run from your default branch.
|
This file contains hidden or 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
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.
Summary
This PR integrates CodSpeed for continuous performance monitoring of spaghettree's core algorithms.
Changes
tests/test_benchmarks.py): 12 benchmarks covering the performance-critical paths:get_dwm(directed weighted modularity) at small, medium, and large matrix scalesAdjMat.from_call_treeconstructionget_merge_pairs,get_top_suggested_merges)optimise_communities).github/workflows/codspeed.yml): Runs benchmarks in simulation mode on pushes tomain, pull requests, and manual dispatch. Uses OIDC authentication.Notes
repo-mapper-rsdev dependency fails to build in current environments (broken maturin config in the published package). The CI workflow and benchmark runs exclude it via--no-install-package repo-mapper-rssince it is not needed for benchmarking.addopts(coverage settings) to avoid failing on coverage thresholds, which are not relevant for performance runs.Next steps
main.optimise_entity_positionspipeline as the project grows.